<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 20 Nov 2026 21:30:44 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-99443</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-99443</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pps: generators: don&amp;#39;t use the driver&amp;#39;s info after unregister&lt;/p&gt;
&lt;p&gt;A file that was opened before pps_gen_unregister_source() keeps
pps_gen, and with it the pointer to the driver&amp;#39;s pps_gen_source_info.
PPS_GEN_SETENABLE and PPS_GEN_USESYSTEMCLOCK keep using that pointer
after the driver has gone:&lt;/p&gt;
&lt;p&gt;- pps_gen_tio allocates its info with devm_kzalloc(), so after an
   unbind both ioctls read freed memory, and SETENABLE calls the
   driver&amp;#39;s enable() with its freed private data.&lt;/p&gt;
&lt;p&gt;- pps_gen-dummy does not set info-&amp;gt;owner, so it can be unloaded while
   the file is open, and the ioctls then read the unloaded module&amp;#39;s
   data and call its code.&lt;/p&gt;
&lt;p&gt;TIO can&amp;#39;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:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;and unloading pps_gen-dummy while its file is open oopses:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffffffffa0203040
  Oops: Oops: 0000 [#1] SMP KASAN NOPTI
  RIP: 0010:pps_gen_cdev_ioctl+0x372/0x580&lt;/p&gt;
&lt;p&gt;Protect info in the ioctl handler with a mutex, and clear it under the…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pps: generators: don&amp;#39;t use the driver&amp;#39;s info after unregister&lt;/p&gt;
&lt;p&gt;A file that was opened before pps_gen_unregister_source() keeps
pps_gen, and with it the pointer to the driver&amp;#39;s pps_gen_source_info.
PPS_GEN_SETENABLE and PPS_GEN_USESYSTEMCLOCK keep using that pointer
after the driver has gone:&lt;/p&gt;
&lt;p&gt;- pps_gen_tio allocates its info with devm_kzalloc(), so after an
   unbind both ioctls read freed memory, and SETENABLE calls the
   driver&amp;#39;s enable() with its freed private data.&lt;/p&gt;
&lt;p&gt;- pps_gen-dummy does not set info-&amp;gt;owner, so it can be unloaded while
   the file is open, and the ioctls then read the unloaded module&amp;#39;s
   data and call its code.&lt;/p&gt;
&lt;p&gt;TIO can&amp;#39;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:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;and unloading pps_gen-dummy while its file is open oopses:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffffffffa0203040
  Oops: Oops: 0000 [#1] SMP KASAN NOPTI
  RIP: 0010:pps_gen_cdev_ioctl+0x372/0x580&lt;/p&gt;
&lt;p&gt;Protect info in the ioctl handler with a mutex, and clear it under the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-99443</guid>
    </item>
    <item>
      <title>GHSA-w4q7-4mhg-vjhx</title>
      <link>https://db.gcve.eu/vuln/ghsa-w4q7-4mhg-vjhx</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pps: generators: don&amp;#39;t use the driver&amp;#39;s info after unregister&lt;/p&gt;
&lt;p&gt;A file that was opened before pps_gen_unregister_source() keeps
pps_gen, and with it the pointer to the driver&amp;#39;s pps_gen_source_info.
PPS_GEN_SETENABLE and PPS_GEN_USESYSTEMCLOCK keep using that pointer
after the driver has gone:&lt;/p&gt;
&lt;p&gt;- pps_gen_tio allocates its info with devm_kzalloc(), so after an
   unbind both ioctls read freed memory, and SETENABLE calls the
   driver&amp;#39;s enable() with its freed private data.&lt;/p&gt;
&lt;p&gt;- pps_gen-dummy does not set info-&amp;gt;owner, so it can be unloaded while
   the file is open, and the ioctls then read the unloaded module&amp;#39;s
   data and call its code.&lt;/p&gt;
&lt;p&gt;TIO can&amp;#39;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:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;and unloading pps_gen-dummy while its file is open oopses:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffffffffa0203040
  Oops: Oops: 0000 [#1] SMP KASAN NOPTI
  RIP: 0010:pps_gen_cdev_ioctl+0x372/0x580&lt;/p&gt;
&lt;p&gt;Protect info in the ioctl handler with a mutex, and clear it under the…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;pps: generators: don&amp;#39;t use the driver&amp;#39;s info after unregister&lt;/p&gt;
&lt;p&gt;A file that was opened before pps_gen_unregister_source() keeps
pps_gen, and with it the pointer to the driver&amp;#39;s pps_gen_source_info.
PPS_GEN_SETENABLE and PPS_GEN_USESYSTEMCLOCK keep using that pointer
after the driver has gone:&lt;/p&gt;
&lt;p&gt;- pps_gen_tio allocates its info with devm_kzalloc(), so after an
   unbind both ioctls read freed memory, and SETENABLE calls the
   driver&amp;#39;s enable() with its freed private data.&lt;/p&gt;
&lt;p&gt;- pps_gen-dummy does not set info-&amp;gt;owner, so it can be unloaded while
   the file is open, and the ioctls then read the unloaded module&amp;#39;s
   data and call its code.&lt;/p&gt;
&lt;p&gt;TIO can&amp;#39;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:&lt;/p&gt;
&lt;p&gt;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&lt;/p&gt;
&lt;p&gt;and unloading pps_gen-dummy while its file is open oopses:&lt;/p&gt;
&lt;p&gt;BUG: unable to handle page fault for address: ffffffffa0203040
  Oops: Oops: 0000 [#1] SMP KASAN NOPTI
  RIP: 0010:pps_gen_cdev_ioctl+0x372/0x580&lt;/p&gt;
&lt;p&gt;Protect info in the ioctl handler with a mutex, and clear it under the…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-w4q7-4mhg-vjhx</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-99443 — pps: generators: don't use the driver's info after unregister</title>
      <link>https://db.gcve.eu/vuln/msrc_cve-2026-99443</link>
      <description>msrc_CVE-2026-99443</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/msrc_cve-2026-99443</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4695 — Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4695</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4695</guid>
    </item>
  </channel>
</rss>
