[PATCH v2 1/4] pps: generators: fix use-after-free when closing a removed device

[PATCH v2 1/4] pps: generators: fix use-after-free when closing a removed device

[Danish Khateeb]

The cdev of a PPS generator is embedded in struct pps_gen_device, but
nothing ties the lifetime of that structure to the cdev: pps_gen is
freed by the release function of its device, and an open file holds a
device reference only until pps_gen_cdev_release() drops it.

When the generator is unregistered while /dev/pps-genN is open, that
put_device() drops the last reference and frees pps_gen, and __fput()
then calls cdev_put() on the freed cdev:

  BUG: KASAN: slab-use-after-free in cdev_put+0x53/0x60
  Read of size 8 at addr ffff88801383e138 by task ppsgen64/149
  Call Trace:
   cdev_put+0x53/0x60
   __fput+0x745/0xad0
   fput_close_sync+0xd9/0x1b0
   __x64_sys_close+0x86/0xf0
  ...
  Freed by task 149:
   kfree+0x25a/0x6d0
   device_release+0xca/0x3c0
   kobject_put+0x169/0x320
   pps_gen_cdev_release+0x51/0x80
   __fput+0x36a/0xad0

pps.c had the same bug, fixed in commit c79a39dc8d06 ("pps: Fix a
use-after-free").

Fix it the usual way: embed the struct device in pps_gen_device and
register both with cdev_device_add(). This makes the device the parent
of the cdev, so the cdev holds a device reference until the last file
is closed.

Fixes: 86b525bed275 ("drivers pps: add PPS generators support")
Cc: stable@vger.kernel.org
Assisted-by: LLM
Signed-off-by: Danish Khateeb <danishkhateeb03@gmail.com>
---

Notes:
    Tested in QEMU (virtme-ng, x86_64, KASAN with kasan_multi_shot, lockdep)
    on v7.3-rc5. pps_gen_tio needs ART and can't probe in a VM, so the test
    uses a small platform driver that registers its generator the way TIO
    does. Unbinding it while /dev/pps-gen0 is open gives the cdev_put()
    report above; with this patch it is gone.
    
    The new registration error paths were run too, under KASAN and kmemleak:
    a 17th generator (-ENOSPC), and failslab fail-nth over each allocation
    of a bind (dev_set_name(), cdev_add(), device_add()). No reports and no
    leaks.

 drivers/pps/generators/pps_gen.c | 63 ++++++++++++++++----------------
 include/linux/pps_gen_kernel.h   |  2 +-
 2 files changed, 32 insertions(+), 33 deletions(-)

diff --git a/drivers/pps/generators/pps_gen.c b/drivers/pps/generators/pps_gen.c
index 5e207c75e340..059f4fe6c9b4 100644
--- a/drivers/pps/generators/pps_gen.c
+++ b/drivers/pps/generators/pps_gen.c
@@ -63,7 +63,7 @@ static long pps_gen_cdev_ioctl(struct file *file,
 
 	switch (cmd) {
 	case PPS_GEN_SETENABLE:
-		dev_dbg(pps_gen->dev, "PPS_GEN_SETENABLE\n");
+		dev_dbg(&pps_gen->dev, "PPS_GEN_SETENABLE\n");
 
 		ret = get_user(status, uiuarg);
 		if (ret)
@@ -77,7 +77,7 @@ static long pps_gen_cdev_ioctl(struct file *file,
 		break;
 
 	case PPS_GEN_USESYSTEMCLOCK:
-		dev_dbg(pps_gen->dev, "PPS_GEN_USESYSTEMCLOCK\n");
+		dev_dbg(&pps_gen->dev, "PPS_GEN_USESYSTEMCLOCK\n");
 
 		ret = put_user(pps_gen->info->use_system_clock, uiuarg);
 		if (ret)
@@ -89,12 +89,12 @@ static long pps_gen_cdev_ioctl(struct file *file,
 		struct pps_gen_event info;
 		unsigned int ev = pps_gen->last_ev;
 
-		dev_dbg(pps_gen->dev, "PPS_GEN_FETCHEVENT\n");
+		dev_dbg(&pps_gen->dev, "PPS_GEN_FETCHEVENT\n");
 
 		ret = wait_event_interruptible(pps_gen->queue,
 				ev != pps_gen->last_ev);
 		if (ret == -ERESTARTSYS) {
-			dev_dbg(pps_gen->dev, "pending signal caught\n");
+			dev_dbg(&pps_gen->dev, "pending signal caught\n");
 			return -EINTR;
 		}
 
@@ -121,7 +121,7 @@ static int pps_gen_cdev_open(struct inode *inode, struct file *file)
 	struct pps_gen_device *pps_gen = container_of(inode->i_cdev,
 				struct pps_gen_device, cdev);
 
-	get_device(pps_gen->dev);
+	get_device(&pps_gen->dev);
 	file->private_data = pps_gen;
 	return 0;
 }
@@ -130,7 +130,7 @@ static int pps_gen_cdev_release(struct inode *inode, struct file *file)
 {
 	struct pps_gen_device *pps_gen = file->private_data;
 
-	put_device(pps_gen->dev);
+	put_device(&pps_gen->dev);
 	return 0;
 }
 
@@ -151,19 +151,15 @@ static void pps_gen_device_destruct(struct device *dev)
 {
 	struct pps_gen_device *pps_gen = dev_get_drvdata(dev);
 
-	cdev_del(&pps_gen->cdev);
-
 	pr_debug("deallocating pps-gen%d\n", pps_gen->id);
 	ida_free(&pps_gen_ida, pps_gen->id);
 
-	kfree(dev);
 	kfree(pps_gen);
 }
 
 static int pps_gen_register_cdev(struct pps_gen_device *pps_gen)
 {
 	int err;
-	dev_t devt;
 
 	err = ida_alloc_max(&pps_gen_ida, PPS_GEN_MAX_SOURCES - 1, GFP_KERNEL);
 	if (err < 0) {
@@ -171,46 +167,52 @@ static int pps_gen_register_cdev(struct pps_gen_device *pps_gen)
 			pr_err("too many PPS sources in the system\n");
 			err = -EBUSY;
 		}
+		kfree(pps_gen);
 		return err;
 	}
 	pps_gen->id = err;
 
-	devt = MKDEV(MAJOR(pps_gen_devt), pps_gen->id);
+	/*
+	 * From here on pps_gen belongs to its device and is freed by
+	 * pps_gen_device_destruct(). The cdev holds a reference to the
+	 * device, so pps_gen stays around until the last file is closed.
+	 */
+	device_initialize(&pps_gen->dev);
+	pps_gen->dev.class = &pps_gen_class;
+	pps_gen->dev.parent = pps_gen->info->parent;
+	pps_gen->dev.devt = MKDEV(MAJOR(pps_gen_devt), pps_gen->id);
+	pps_gen->dev.release = pps_gen_device_destruct;
+	dev_set_drvdata(&pps_gen->dev, pps_gen);
 
 	cdev_init(&pps_gen->cdev, &pps_gen_cdev_fops);
 	pps_gen->cdev.owner = pps_gen->info->owner;
 
-	err = cdev_add(&pps_gen->cdev, devt, 1);
+	err = dev_set_name(&pps_gen->dev, "pps-gen%d", pps_gen->id);
+	if (err)
+		goto put_dev;
+
+	err = cdev_device_add(&pps_gen->cdev, &pps_gen->dev);
 	if (err) {
 		pr_err("failed to add char device %d:%d\n",
 				MAJOR(pps_gen_devt), pps_gen->id);
-		goto free_ida;
+		goto put_dev;
 	}
-	pps_gen->dev = device_create(&pps_gen_class, pps_gen->info->parent, devt,
-				     pps_gen, "pps-gen%d", pps_gen->id);
-	if (IS_ERR(pps_gen->dev)) {
-		err = PTR_ERR(pps_gen->dev);
-		goto del_cdev;
-	}
-	pps_gen->dev->release = pps_gen_device_destruct;
-	dev_set_drvdata(pps_gen->dev, pps_gen);
 
 	pr_debug("generator got cdev (%d:%d)\n",
 			MAJOR(pps_gen_devt), pps_gen->id);
 
 	return 0;
 
-del_cdev:
-	cdev_del(&pps_gen->cdev);
-free_ida:
-	ida_free(&pps_gen_ida, pps_gen->id);
+put_dev:
+	put_device(&pps_gen->dev);
 	return err;
 }
 
 static void pps_gen_unregister_cdev(struct pps_gen_device *pps_gen)
 {
 	pr_debug("unregistering pps-gen%d\n", pps_gen->id);
-	device_destroy(&pps_gen_class, pps_gen->dev->devt);
+	cdev_device_del(&pps_gen->cdev, &pps_gen->dev);
+	put_device(&pps_gen->dev);
 }
 
 /*
@@ -244,18 +246,15 @@ struct pps_gen_device *pps_gen_register_source(const struct pps_gen_source_info
 	init_waitqueue_head(&pps_gen->queue);
 	spin_lock_init(&pps_gen->lock);
 
-	/* Create the char device */
+	/* Create the char device, this frees pps_gen on failure */
 	err = pps_gen_register_cdev(pps_gen);
 	if (err < 0) {
 		pr_err(" unable to create char device\n");
-		goto kfree_pps_gen;
+		goto pps_gen_register_source_exit;
 	}
 
 	return pps_gen;
 
-kfree_pps_gen:
-	kfree(pps_gen);
-
 pps_gen_register_source_exit:
 	pr_err("unable to register generator\n");
 
@@ -289,7 +288,7 @@ void pps_gen_event(struct pps_gen_device *pps_gen,
 {
 	unsigned long flags;
 
-	dev_dbg(pps_gen->dev, "PPS generator event %u\n", event);
+	dev_dbg(&pps_gen->dev, "PPS generator event %u\n", event);
 
 	spin_lock_irqsave(&pps_gen->lock, flags);
 
diff --git a/include/linux/pps_gen_kernel.h b/include/linux/pps_gen_kernel.h
index 6214c8aa2e02..f26f6aac000d 100644
--- a/include/linux/pps_gen_kernel.h
+++ b/include/linux/pps_gen_kernel.h
@@ -54,7 +54,7 @@ struct pps_gen_device {
 
 	unsigned int id;			/* PPS generator unique ID */
 	struct cdev cdev;
-	struct device *dev;
+	struct device dev;
 	struct fasync_struct *async_queue;	/* fasync method */
 	spinlock_t lock;
 };
-- 
2.55.0

Re: [PATCH v2 1/4] pps: generators: fix use-after-free when closing a removed device

[Rodolfo Giometti]

On Tue, 29 Sep 2026 07:49:34 -0500, Danish Khateeb wrote:
> The cdev of a PPS generator is embedded in struct pps_gen_device, but
> nothing ties the lifetime of that structure to the cdev: pps_gen is
> freed by the release function of its device, and an open file holds a
> device reference only until pps_gen_cdev_release() drops it.
>
> When the generator is unregistered while /dev/pps-genN is open, that
> put_device() drops the last reference and frees pps_gen, and __fput()
> then calls cdev_put() on the freed cdev:
>
>   BUG: KASAN: slab-use-after-free in cdev_put+0x53/0x60
>   Read of size 8 at addr ffff88801383e138 by task ppsgen64/149
>   Call Trace:
>    cdev_put+0x53/0x60
>    __fput+0x745/0xad0
>    fput_close_sync+0xd9/0x1b0
>    __x64_sys_close+0x86/0xf0
>   ...
>   Freed by task 149:
>    kfree+0x25a/0x6d0
>    device_release+0xca/0x3c0
>    kobject_put+0x169/0x320
>    pps_gen_cdev_release+0x51/0x80
>    __fput+0x36a/0xad0
>
> pps.c had the same bug, fixed in commit c79a39dc8d06 ("pps: Fix a
> use-after-free").
>
> Fix it the usual way: embed the struct device in pps_gen_device and
> register both with cdev_device_add(). This makes the device the parent
> of the cdev, so the cdev holds a device reference until the last file
> is closed.
>
> Fixes: 86b525bed275 ("drivers pps: add PPS generators support")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Danish Khateeb <danishkhateeb03@gmail.com>

Acked-by: Rodolfo Giometti <giometti@enneenne.com>

[PATCH v2 2/4] pps: generators: don't use the driver's info after unregister

[Danish Khateeb]

A file that was opened before pps_gen_unregister_source() keeps
pps_gen, and with it the pointer to the driver's pps_gen_source_info.
PPS_GEN_SETENABLE and PPS_GEN_USESYSTEMCLOCK keep using that pointer
after the driver has gone:

 - pps_gen_tio allocates its info with devm_kzalloc(), so after an
   unbind both ioctls read freed memory, and SETENABLE calls the
   driver's enable() with its freed private data.

 - pps_gen-dummy does not set info->owner, so it can be unloaded while
   the file is open, and the ioctls then read the unloaded module's
   data and call its code.

TIO can't probe in a VM, as it needs ART. A test driver that registers
its info in devm memory like TIO does, unbound while /dev/pps-gen0 is
open, gives:

  BUG: KASAN: slab-use-after-free in pps_gen_cdev_ioctl+0x4c1/0x580
  Read of size 1 at addr ffff88800e647f38 by task ppsgen64/145
  ...
  Freed by task 146:
   kfree+0x25a/0x6d0
   release_nodes+0xd1/0x140
   devres_release_all+0x10e/0x1a0
   device_unbind_cleanup+0x71/0x250
   device_release_driver_internal+0x41b/0x570
   unbind_store+0xd9/0x100

and unloading pps_gen-dummy while its file is open oopses:

  BUG: unable to handle page fault for address: ffffffffa0203040
  Oops: Oops: 0000 [#1] SMP KASAN NOPTI
  RIP: 0010:pps_gen_cdev_ioctl+0x372/0x580

Protect info in the ioctl handler with a mutex, and clear it under the
mutex on unregister, so that unregister waits for the ioctls using it
and later ones fail with -ENODEV. PPS_KC_BIND does the same for a
removed PPS device since commit 3649f9a6b897 ("pps: don't allow
PPS_KC_BIND on removed devices"). The sysfs attributes need nothing
new: they are removed, and their callbacks drained, before info is
cleared.

Fixes: 86b525bed275 ("drivers pps: add PPS generators support")
Cc: stable@vger.kernel.org
Assisted-by: LLM
Signed-off-by: Danish Khateeb <danishkhateeb03@gmail.com>
---

Notes:
    Tested in the same setup, with patch 1/4 applied. After an unbind, and
    after unloading pps_gen-dummy with its file open, both ioctls return
    -ENODEV with no KASAN report, and closing the file is clean. Normal use
    of pps_gen-dummy is unchanged.

 drivers/pps/generators/pps_gen.c | 31 ++++++++++++++++++++++++++-----
 include/linux/pps_gen_kernel.h   |  2 ++
 2 files changed, 28 insertions(+), 5 deletions(-)

diff --git a/drivers/pps/generators/pps_gen.c b/drivers/pps/generators/pps_gen.c
index 059f4fe6c9b4..d80e28dc31dc 100644
--- a/drivers/pps/generators/pps_gen.c
+++ b/drivers/pps/generators/pps_gen.c
@@ -69,17 +69,28 @@ static long pps_gen_cdev_ioctl(struct file *file,
 		if (ret)
 			return -EFAULT;
 
-		ret = pps_gen->info->enable(pps_gen, status);
-		if (ret)
-			return ret;
-		pps_gen->enabled = status;
+		scoped_guard(mutex, &pps_gen->info_lock) {
+			if (!pps_gen->info)
+				return -ENODEV;
+
+			ret = pps_gen->info->enable(pps_gen, status);
+			if (ret)
+				return ret;
+			pps_gen->enabled = status;
+		}
 
 		break;
 
 	case PPS_GEN_USESYSTEMCLOCK:
 		dev_dbg(&pps_gen->dev, "PPS_GEN_USESYSTEMCLOCK\n");
 
-		ret = put_user(pps_gen->info->use_system_clock, uiuarg);
+		scoped_guard(mutex, &pps_gen->info_lock) {
+			if (!pps_gen->info)
+				return -ENODEV;
+			status = pps_gen->info->use_system_clock;
+		}
+
+		ret = put_user(status, uiuarg);
 		if (ret)
 			return -EFAULT;
 
@@ -212,6 +223,15 @@ static void pps_gen_unregister_cdev(struct pps_gen_device *pps_gen)
 {
 	pr_debug("unregistering pps-gen%d\n", pps_gen->id);
 	cdev_device_del(&pps_gen->cdev, &pps_gen->dev);
+
+	/*
+	 * An open file keeps pps_gen around, but the driver may free info as
+	 * soon as we return. The sysfs files are gone now, so wait for the
+	 * ioctls using info and make later ones fail.
+	 */
+	scoped_guard(mutex, &pps_gen->info_lock)
+		pps_gen->info = NULL;
+
 	put_device(&pps_gen->dev);
 }
 
@@ -243,6 +263,7 @@ struct pps_gen_device *pps_gen_register_source(const struct pps_gen_source_info
 	pps_gen->info = info;
 	pps_gen->enabled = false;
 
+	mutex_init(&pps_gen->info_lock);
 	init_waitqueue_head(&pps_gen->queue);
 	spin_lock_init(&pps_gen->lock);
 
diff --git a/include/linux/pps_gen_kernel.h b/include/linux/pps_gen_kernel.h
index f26f6aac000d..c4d22b1af118 100644
--- a/include/linux/pps_gen_kernel.h
+++ b/include/linux/pps_gen_kernel.h
@@ -11,6 +11,7 @@
 #include <linux/pps_gen.h>
 #include <linux/cdev.h>
 #include <linux/device.h>
+#include <linux/mutex.h>
 
 /*
  * Global defines
@@ -44,6 +45,7 @@ struct pps_gen_source_info {
 /* The main struct */
 struct pps_gen_device {
 	const struct pps_gen_source_info *info;	/* PSS generator info */
+	struct mutex info_lock;			/* protects info */
 	bool enabled;				/* PSS generator status */
 
 	unsigned int event;
-- 
2.55.0

Re: [PATCH v2 2/4] pps: generators: don't use the driver's info after unregister

[Rodolfo Giometti]

On Tue, 29 Sep 2026 07:49:35 -0500, Danish Khateeb wrote:
> A file that was opened before pps_gen_unregister_source() keeps
> pps_gen, and with it the pointer to the driver's pps_gen_source_info.
> PPS_GEN_SETENABLE and PPS_GEN_USESYSTEMCLOCK keep using that pointer
> after the driver has gone:
>
>  - pps_gen_tio allocates its info with devm_kzalloc(), so after an
>    unbind both ioctls read freed memory, and SETENABLE calls the
>    driver's enable() with its freed private data.
>
>  - pps_gen-dummy does not set info->owner, so it can be unloaded while
>    the file is open, and the ioctls then read the unloaded module's
>    data and call its code.
>
> TIO can't probe in a VM, as it needs ART. A test driver that registers
> its info in devm memory like TIO does, unbound while /dev/pps-gen0 is
> open, gives:
>
>   BUG: KASAN: slab-use-after-free in pps_gen_cdev_ioctl+0x4c1/0x580
>   Read of size 1 at addr ffff88800e647f38 by task ppsgen64/145
>   ...
>   Freed by task 146:
>    kfree+0x25a/0x6d0
>    release_nodes+0xd1/0x140
>    devres_release_all+0x10e/0x1a0
>    device_unbind_cleanup+0x71/0x250
>    device_release_driver_internal+0x41b/0x570
>    unbind_store+0xd9/0x100
>
> and unloading pps_gen-dummy while its file is open oopses:
>
>   BUG: unable to handle page fault for address: ffffffffa0203040
>   Oops: Oops: 0000 [#1] SMP KASAN NOPTI
>   RIP: 0010:pps_gen_cdev_ioctl+0x372/0x580
>
> Protect info in the ioctl handler with a mutex, and clear it under the
> mutex on unregister, so that unregister waits for the ioctls using it
> and later ones fail with -ENODEV. PPS_KC_BIND does the same for a
> removed PPS device since commit 3649f9a6b897 ("pps: don't allow
> PPS_KC_BIND on removed devices"). The sysfs attributes need nothing
> new: they are removed, and their callbacks drained, before info is
> cleared.
>
> Fixes: 86b525bed275 ("drivers pps: add PPS generators support")
> Cc: stable@vger.kernel.org
> Assisted-by: LLM
> Signed-off-by: Danish Khateeb <danishkhateeb03@gmail.com>
> ---
>
> Notes:
>     Tested in the same setup, with patch 1/4 applied. After an unbind, and
>     after unloading pps_gen-dummy with its file open, both ioctls return
>     -ENODEV with no KASAN report, and closing the file is clean. Normal use
>     of pps_gen-dummy is unchanged.
>
>  drivers/pps/generators/pps_gen.c | 31 ++++++++++++++++++++++++++-----
>  include/linux/pps_gen_kernel.h   |  2 ++
>  2 files changed, 28 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/pps/generators/pps_gen.c b/drivers/pps/generators/pps_gen.c
> index 059f4fe6c9b4..d80e28dc31dc 100644
> --- a/drivers/pps/generators/pps_gen.c
> +++ b/drivers/pps/generators/pps_gen.c
> @@ -69,17 +69,28 @@ static long pps_gen_cdev_ioctl(struct file *file,
>  		if (ret)
>  			return -EFAULT;
>  
> -		ret = pps_gen->info->enable(pps_gen, status);
> -		if (ret)
> -			return ret;
> -		pps_gen->enabled = status;
> +		scoped_guard(mutex, &pps_gen->info_lock) {
> +			if (!pps_gen->info)
> +				return -ENODEV;
> +
> +			ret = pps_gen->info->enable(pps_gen, status);
> +			if (ret)
> +				return ret;
> +			pps_gen->enabled = status;
> +		}
>  
>  		break;
>  
>  	case PPS_GEN_USESYSTEMCLOCK:
>  		dev_dbg(&pps_gen->dev, "PPS_GEN_USESYSTEMCLOCK\n");
>  
> -		ret = put_user(pps_gen->info->use_system_clock, uiuarg);
> +		scoped_guard(mutex, &pps_gen->info_lock) {
> +			if (!pps_gen->info)
> +				return -ENODEV;
> +			status = pps_gen->info->use_system_clock;
> +		}
> +
> +		ret = put_user(status, uiuarg);
>  		if (ret)
>  			return -EFAULT;
>  
> @@ -212,6 +223,15 @@ static void pps_gen_unregister_cdev(struct pps_gen_device *pps_gen)
>  {
>  	pr_debug("unregistering pps-gen%d\n", pps_gen->id);
>  	cdev_device_del(&pps_gen->cdev, &pps_gen->dev);
> +
> +	/*
> +	 * An open file keeps pps_gen around, but the driver may free info as
> +	 * soon as we return. The sysfs files are gone now, so wait for the
> +	 * ioctls using info and make later ones fail.
> +	 */
> +	scoped_guard(mutex, &pps_gen->info_lock)
> +		pps_gen->info = NULL;
> +
>  	put_device(&pps_gen->dev);
>  }
>  
> @@ -243,6 +263,7 @@ struct pps_gen_device *pps_gen_register_source(const struct pps_gen_source_info
>  	pps_gen->info = info;
>  	pps_gen->enabled = false;
>  
> +	mutex_init(&pps_gen->info_lock);
>  	init_waitqueue_head(&pps_gen->queue);
>  	spin_lock_init(&pps_gen->lock);
>  
> diff --git a/include/linux/pps_gen_kernel.h b/include/linux/pps_gen_kernel.h
> index f26f6aac000d..c4d22b1af118 100644
> --- a/include/linux/pps_gen_kernel.h
> +++ b/include/linux/pps_gen_kernel.h
> @@ -11,6 +11,7 @@
>  #include <linux/pps_gen.h>
>  #include <linux/cdev.h>
>  #include <linux/device.h>
> +#include <linux/mutex.h>
>  
>  /*
>   * Global defines
> @@ -44,6 +45,7 @@ struct pps_gen_source_info {
>  /* The main struct */
>  struct pps_gen_device {
>  	const struct pps_gen_source_info *info;	/* PSS generator info */
> +	struct mutex info_lock;			/* protects info */
>  	bool enabled;				/* PSS generator status */
>  
>  	unsigned int event;

Acked-by: Rodolfo Giometti <giometti@enneenne.com>

[PATCH v2 3/4] pps: generators: stop the generator on unregister

[Danish Khateeb]

Both generator drivers stop their timer and then call
pps_gen_unregister_source(): pps_gen_tio_remove() cancels its hrtimer
and disables the TIO, and pps_gen_dummy_exit() deletes its timer. But
/dev/pps-genN and the sysfs "enable" attribute are still there until
the unregister, and a PPS_GEN_SETENABLE or a write to "enable" in
between starts the timer again. Nothing stops it after that: TIO's
hrtimer keeps running in the devm memory freed by the unbind, and the
dummy's timer is left in the unloaded module.

The drivers can't avoid this by unregistering first, as TIO's timer
callback uses pps_gen, which the unregister may free.

Stop the generator in pps_gen_unregister_cdev() instead, under
info_lock after the device and its sysfs files are gone, when nothing
can enable it again. pps_gen_unregister_source() then also does what
its kernel-doc says: "it disables the generator so no pulses are
generated anymore".

Fixes: 86b525bed275 ("drivers pps: add PPS generators support")
Cc: stable@vger.kernel.org
Suggested-by: Rodolfo Giometti <giometti@enneenne.com>
Assisted-by: LLM
Signed-off-by: Danish Khateeb <danishkhateeb03@gmail.com>
---

Notes:
    Tested in the same setup, with patches 1/4 and 2/4 applied. The test
    driver got a periodic hrtimer in its devm memory, like TIO's, and a
    remove() that cancels it and then enables the generator again before
    unregistering, as a PPS_GEN_SETENABLE landing there would. Without this
    patch the timer keeps running after the unbind:
    
      BUG: KASAN: slab-use-after-free in rb_erase+0x174d/0x1a70
       __remove_hrtimer+0x138/0x450
       __hrtimer_run_queues+0x2c5/0x7f0
       hrtimer_interrupt+0x3db/0x910
      ...
      Freed by task 175:
       kfree+0x25a/0x6d0
       release_nodes+0xd1/0x140
       devres_release_all+0x10e/0x1a0
       device_unbind_cleanup+0x71/0x250
       device_release_driver_internal+0x41b/0x570
       unbind_store+0xd9/0x100
    
    With it, unregister calls enable(false), the timer is stopped, and
    there are no reports. Unbinding the test driver while enabled, and
    unloading pps_gen-dummy while its file is open and enabled, are clean
    too.

 drivers/pps/generators/pps_gen.c | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/drivers/pps/generators/pps_gen.c b/drivers/pps/generators/pps_gen.c
index d80e28dc31dc..452cc12a96f2 100644
--- a/drivers/pps/generators/pps_gen.c
+++ b/drivers/pps/generators/pps_gen.c
@@ -228,9 +228,18 @@ static void pps_gen_unregister_cdev(struct pps_gen_device *pps_gen)
 	 * An open file keeps pps_gen around, but the driver may free info as
 	 * soon as we return. The sysfs files are gone now, so wait for the
 	 * ioctls using info and make later ones fail.
+	 *
+	 * The driver may have stopped the generator before calling us, but
+	 * userspace could have enabled it again since. Nothing can enable it
+	 * after this point, so stop it here for good.
 	 */
-	scoped_guard(mutex, &pps_gen->info_lock)
+	scoped_guard(mutex, &pps_gen->info_lock) {
+		if (pps_gen->enabled) {
+			pps_gen->info->enable(pps_gen, false);
+			pps_gen->enabled = false;
+		}
 		pps_gen->info = NULL;
+	}
 
 	put_device(&pps_gen->dev);
 }
-- 
2.55.0

Re: [PATCH v2 3/4] pps: generators: stop the generator on unregister

[Rodolfo Giometti]

On Tue, 29 Sep 2026 07:49:36 -0500, Danish Khateeb wrote:
> Both generator drivers stop their timer and then call
> pps_gen_unregister_source(): pps_gen_tio_remove() cancels its hrtimer
> and disables the TIO, and pps_gen_dummy_exit() deletes its timer. But
> /dev/pps-genN and the sysfs "enable" attribute are still there until
> the unregister, and a PPS_GEN_SETENABLE or a write to "enable" in
> between starts the timer again. Nothing stops it after that: TIO's
> hrtimer keeps running in the devm memory freed by the unbind, and the
> dummy's timer is left in the unloaded module.
>
> The drivers can't avoid this by unregistering first, as TIO's timer
> callback uses pps_gen, which the unregister may free.
>
> Stop the generator in pps_gen_unregister_cdev() instead, under
> info_lock after the device and its sysfs files are gone, when nothing
> can enable it again. pps_gen_unregister_source() then also does what
> its kernel-doc says: "it disables the generator so no pulses are
> generated anymore".
>
> Fixes: 86b525bed275 ("drivers pps: add PPS generators support")
> Cc: stable@vger.kernel.org
> Suggested-by: Rodolfo Giometti <giometti@enneenne.com>
> Assisted-by: LLM
> Signed-off-by: Danish Khateeb <danishkhateeb03@gmail.com>
> ---
>
> Notes:
>     Tested in the same setup, with patches 1/4 and 2/4 applied. The test
>     driver got a periodic hrtimer in its devm memory, like TIO's, and a
>     remove() that cancels it and then enables the generator again before
>     unregistering, as a PPS_GEN_SETENABLE landing there would. Without this
>     patch the timer keeps running after the unbind:
>     
>       BUG: KASAN: slab-use-after-free in rb_erase+0x174d/0x1a70
>        __remove_hrtimer+0x138/0x450
>        __hrtimer_run_queues+0x2c5/0x7f0
>        hrtimer_interrupt+0x3db/0x910
>       ...
>       Freed by task 175:
>        kfree+0x25a/0x6d0
>        release_nodes+0xd1/0x140
>        devres_release_all+0x10e/0x1a0
>        device_unbind_cleanup+0x71/0x250
>        device_release_driver_internal+0x41b/0x570
>        unbind_store+0xd9/0x100
>     
>     With it, unregister calls enable(false), the timer is stopped, and
>     there are no reports. Unbinding the test driver while enabled, and
>     unloading pps_gen-dummy while its file is open and enabled, are clean
>     too.
>
>  drivers/pps/generators/pps_gen.c | 11 ++++++++++-
>  1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pps/generators/pps_gen.c b/drivers/pps/generators/pps_gen.c
> index d80e28dc31dc..452cc12a96f2 100644
> --- a/drivers/pps/generators/pps_gen.c
> +++ b/drivers/pps/generators/pps_gen.c
> @@ -228,9 +228,18 @@ static void pps_gen_unregister_cdev(struct pps_gen_device *pps_gen)
>  	 * An open file keeps pps_gen around, but the driver may free info as
>  	 * soon as we return. The sysfs files are gone now, so wait for the
>  	 * ioctls using info and make later ones fail.
> +	 *
> +	 * The driver may have stopped the generator before calling us, but
> +	 * userspace could have enabled it again since. Nothing can enable it
> +	 * after this point, so stop it here for good.
>  	 */
> -	scoped_guard(mutex, &pps_gen->info_lock)
> +	scoped_guard(mutex, &pps_gen->info_lock) {
> +		if (pps_gen->enabled) {
> +			pps_gen->info->enable(pps_gen, false);
> +			pps_gen->enabled = false;
> +		}
>  		pps_gen->info = NULL;
> +	}
>  
>  	put_device(&pps_gen->dev);
>  }

Acked-by: Rodolfo Giometti <giometti@enneenne.com>