<?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>Thu, 19 Nov 2026 17:56:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38473 — Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb()</title>
      <link>https://db.gcve.eu/vuln/cve-2025-38473</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb()&lt;/p&gt;
&lt;p&gt;syzbot reported null-ptr-deref in l2cap_sock_resume_cb(). [0]&lt;/p&gt;
&lt;p&gt;l2cap_sock_resume_cb() has a similar problem that was fixed by commit
1bff51ea59a9 (&amp;#34;Bluetooth: fix use-after-free error in lock_sock_nested()&amp;#34;).&lt;/p&gt;
&lt;p&gt;Since both l2cap_sock_kill() and l2cap_sock_resume_cb() are executed
under l2cap_sock_resume_cb(), we can avoid the issue simply by checking
if chan-&amp;gt;data is NULL.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s not access to the killed socket in l2cap_sock_resume_cb().&lt;/p&gt;
&lt;p&gt;[0]:
BUG: KASAN: null-ptr-deref in instrument_atomic_write include/linux/instrumented.h:82 [inline]
BUG: KASAN: null-ptr-deref in clear_bit include/asm-generic/bitops/instrumented-atomic.h:41 [inline]
BUG: KASAN: null-ptr-deref in l2cap_sock_resume_cb+0xb4/0x17c net/bluetooth/l2cap_sock.c:1711
Write of size 8 at addr 0000000000000570 by task kworker/u9:0/52&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 52 Comm: kworker/u9:0 Not tainted 6.16.0-rc4-syzkaller-g7482bb149b9f #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: hci0 hci_rx_work
Call trace:
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:501 (C)
 __dump_stack+0x30/0x40 lib/dump_stack.c:94
 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120
 print_report+0x58/0x84 mm/kasan/report.c:524
 kasan_report+0xb0/0x110 mm/kasan/report.c:634
 check_region_inline mm/kasan/generic.c:-1 [inline]
 kasan_check_range+0x264/0x2a4 mm/kasan/gene…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Bluetooth: Fix null-ptr-deref in l2cap_sock_resume_cb()&lt;/p&gt;
&lt;p&gt;syzbot reported null-ptr-deref in l2cap_sock_resume_cb(). [0]&lt;/p&gt;
&lt;p&gt;l2cap_sock_resume_cb() has a similar problem that was fixed by commit
1bff51ea59a9 (&amp;#34;Bluetooth: fix use-after-free error in lock_sock_nested()&amp;#34;).&lt;/p&gt;
&lt;p&gt;Since both l2cap_sock_kill() and l2cap_sock_resume_cb() are executed
under l2cap_sock_resume_cb(), we can avoid the issue simply by checking
if chan-&amp;gt;data is NULL.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s not access to the killed socket in l2cap_sock_resume_cb().&lt;/p&gt;
&lt;p&gt;[0]:
BUG: KASAN: null-ptr-deref in instrument_atomic_write include/linux/instrumented.h:82 [inline]
BUG: KASAN: null-ptr-deref in clear_bit include/asm-generic/bitops/instrumented-atomic.h:41 [inline]
BUG: KASAN: null-ptr-deref in l2cap_sock_resume_cb+0xb4/0x17c net/bluetooth/l2cap_sock.c:1711
Write of size 8 at addr 0000000000000570 by task kworker/u9:0/52&lt;/p&gt;
&lt;p&gt;CPU: 1 UID: 0 PID: 52 Comm: kworker/u9:0 Not tainted 6.16.0-rc4-syzkaller-g7482bb149b9f #0 PREEMPT
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: hci0 hci_rx_work
Call trace:
 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:501 (C)
 __dump_stack+0x30/0x40 lib/dump_stack.c:94
 dump_stack_lvl+0xd8/0x12c lib/dump_stack.c:120
 print_report+0x58/0x84 mm/kasan/report.c:524
 kasan_report+0xb0/0x110 mm/kasan/report.c:634
 check_region_inline mm/kasan/generic.c:-1 [inline]
 kasan_check_range+0x264/0x2a4 mm/kasan/gene…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-38473</guid>
    </item>
    <item>
      <title>USN-7879-1 — linux, linux-aws, linux-gcp, linux-hwe-6.14, linux-oracle, linux-realtime vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-7879-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.14&lt;/p&gt;
&lt;p&gt;It was discovered that improper initialization of CPU cache memory could
allow a local attacker with hypervisor access to overwrite SEV-SNP guest
memory resulting in loss of data integrity. (CVE-2024-36331)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Network block device driver;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - Powercap sysfs driver;
  - Voltage and Current Regulator drivers;
  - S/390 drivers;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - small TFT LCD display modules;
  - Media staging drivers;
  - USB Gadget drivers;
  - vDPA drivers;
  - VFIO drivers;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ceph distributed file sy…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-6.14&lt;/p&gt;
&lt;p&gt;It was discovered that improper initialization of CPU cache memory could
allow a local attacker with hypervisor access to overwrite SEV-SNP guest
memory resulting in loss of data integrity. (CVE-2024-36331)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM64 architecture;
  - PowerPC architecture;
  - S390 architecture;
  - x86 architecture;
  - Network block device driver;
  - Character device driver;
  - Clock framework and drivers;
  - Data acquisition framework and drivers;
  - Hardware crypto device drivers;
  - Device frequency scaling framework;
  - DMA engine subsystem;
  - EDAC drivers;
  - GPU drivers;
  - HID subsystem;
  - Hardware monitoring drivers;
  - I2C subsystem;
  - IIO subsystem;
  - IIO ADC drivers;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Multiple devices driver;
  - Media drivers;
  - Network drivers;
  - Mellanox network drivers;
  - PCI subsystem;
  - PHY drivers;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - Power supply drivers;
  - Powercap sysfs driver;
  - Voltage and Current Regulator drivers;
  - S/390 drivers;
  - ASPEED SoC drivers;
  - SPI subsystem;
  - small TFT LCD display modules;
  - Media staging drivers;
  - USB Gadget drivers;
  - vDPA drivers;
  - VFIO drivers;
  - Framebuffer layer;
  - Xen hypervisor drivers;
  - BTRFS file system;
  - Ceph distributed file sy…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7879-1</guid>
    </item>
  </channel>
</rss>
