<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T08:42:17.267237+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/alsa-2026:49871</id>
    <title>ALSA-2026:49871 — Moderate: kernel security, bug fix, and enhancement update</title>
    <updated>2026-10-03T08:42:17.436017+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:10: kernel, AlmaLinux:10: kernel-64k, AlmaLinux:10: kernel-64k-core, AlmaLinux:10: kernel-64k-debug, AlmaLinux:10: kernel-64k-debug-core, AlmaLinux:10: kernel-64k-debug-devel, AlmaLinux:10: kernel-64k-debug-devel-matched, AlmaLinux:10: kernel-64k-debug-modules, AlmaLinux:10: kernel-64k-debug-modules-core, AlmaLinux:10: kernel-64k-debug-modules-extra and 65 more</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* kernel: Linux kernel: Denial of Service due to NULL function pointer race in timer shutdown (CVE-2025-68214)
  * kernel: procfs: avoid fetching build ID while holding VMA lock (CVE-2026-23199)</p>
<p>Bug Fix(es) and Enhancement(s):</p>
<p>* [Lenovo] Graphics not working on T14 G7 Intel (Pantherlake) (JIRA:AlmaLinux-172832)
  * Possible regression with FM350GL [almalinux-10.2.z] (JIRA:AlmaLinux-184266)
  * [10.2 FEAT] CNB102: dpll: sync with upstream (JIRA:AlmaLinux-211011)
  * backport make module and modules-core provides use variant [almalinux-10.2.z] (JIRA:AlmaLinux-213965)</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/alsa-2026:49871"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2026-12161</id>
    <title>bdu:2026-12161</title>
    <updated>2026-10-03T08:42:17.436161+00:00</updated>
    <content>bdu:2026-12161</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-12161"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-23199</id>
    <title>BELL-CVE-2026-23199</title>
    <updated>2026-10-03T08:42:17.436180+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-23199"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0192</id>
    <title>certfr-2026-avi-0192 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
    <updated>2026-10-03T08:42:17.436200+00:00</updated>
    <content>certfr-2026-avi-0192</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-0192"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-315404</id>
    <title>EUVD-2026-315404</title>
    <updated>2026-10-03T08:42:17.436216+00:00</updated>
    <content>EUVD-2026-315404</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-315404"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23199</id>
    <title>fkie_cve-2026-23199</title>
    <updated>2026-10-03T08:42:17.436227+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>procfs: avoid fetching build ID while holding VMA lock</p>
<p>Fix PROCMAP_QUERY to fetch optional build ID only after dropping mmap_lock
or per-VMA lock, whichever was used to lock VMA under question, to avoid
deadlock reported by syzbot:</p>
<p>-&gt; #1 (&amp;mm-&gt;mmap_lock){++++}-{4:4}:
        __might_fault+0xed/0x170
        _copy_to_iter+0x118/0x1720
        copy_page_to_iter+0x12d/0x1e0
        filemap_read+0x720/0x10a0
        blkdev_read_iter+0x2b5/0x4e0
        vfs_read+0x7f4/0xae0
        ksys_read+0x12a/0x250
        do_syscall_64+0xcb/0xf80
        entry_SYSCALL_64_after_hwframe+0x77/0x7f</p>
<p>-&gt; #0 (&amp;sb-&gt;s_type-&gt;i_mutex_key#8){++++}-{4:4}:
        __lock_acquire+0x1509/0x26d0
        lock_acquire+0x185/0x340
        down_read+0x98/0x490
        blkdev_read_iter+0x2a7/0x4e0
        __kernel_read+0x39a/0xa90
        freader_fetch+0x1d5/0xa80
        __build_id_parse.isra.0+0xea/0x6a0
        do_procmap_query+0xd75/0x1050
        procfs_procmap_ioctl+0x7a/0xb0
        __x64_sys_ioctl+0x18e/0x210
        do_syscall_64+0xcb/0xf80
        entry_SYSCALL_64_after_hwframe+0x77/0x7f</p>
<p>other info that might help us debug this:</p>
<p>Possible unsafe locking scenario:</p>
<p>CPU0                    CPU1
        ----                    ----
   rlock(&amp;mm-&gt;mmap_lock);
                                lock(&amp;sb-&gt;s_type-&gt;i_mutex_key#8);
                                lock(&amp;mm-&gt;mmap_lock);
   rlock(&amp;sb-&gt;s_type-&gt;i_mutex_key#8);</p>
<p>*** DE…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-23199"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-hjgx-24cq-764x</id>
    <title>GHSA-hjgx-24cq-764x</title>
    <updated>2026-10-03T08:42:17.436275+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>procfs: avoid fetching build ID while holding VMA lock</p>
<p>Fix PROCMAP_QUERY to fetch optional build ID only after dropping mmap_lock
or per-VMA lock, whichever was used to lock VMA under question, to avoid
deadlock reported by syzbot:</p>
<p>-&gt; #1 (&amp;mm-&gt;mmap_lock){++++}-{4:4}:
        __might_fault+0xed/0x170
        _copy_to_iter+0x118/0x1720
        copy_page_to_iter+0x12d/0x1e0
        filemap_read+0x720/0x10a0
        blkdev_read_iter+0x2b5/0x4e0
        vfs_read+0x7f4/0xae0
        ksys_read+0x12a/0x250
        do_syscall_64+0xcb/0xf80
        entry_SYSCALL_64_after_hwframe+0x77/0x7f</p>
<p>-&gt; #0 (&amp;sb-&gt;s_type-&gt;i_mutex_key#8){++++}-{4:4}:
        __lock_acquire+0x1509/0x26d0
        lock_acquire+0x185/0x340
        down_read+0x98/0x490
        blkdev_read_iter+0x2a7/0x4e0
        __kernel_read+0x39a/0xa90
        freader_fetch+0x1d5/0xa80
        __build_id_parse.isra.0+0xea/0x6a0
        do_procmap_query+0xd75/0x1050
        procfs_procmap_ioctl+0x7a/0xb0
        __x64_sys_ioctl+0x18e/0x210
        do_syscall_64+0xcb/0xf80
        entry_SYSCALL_64_after_hwframe+0x77/0x7f</p>
<p>other info that might help us debug this:</p>
<p>Possible unsafe locking scenario:</p>
<p>CPU0                    CPU1
        ----                    ----
   rlock(&amp;mm-&gt;mmap_lock);
                                lock(&amp;sb-&gt;s_type-&gt;i_mutex_key#8);
                                lock(&amp;mm-&gt;mmap_lock);
   rlock(&amp;sb-&gt;s_type-&gt;i_mutex_key#8);</p>
<p>*** DE…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-hjgx-24cq-764x"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:49871</id>
    <title>RHSA-2026:49871 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
    <updated>2026-10-03T08:42:17.436312+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>kernel: Linux kernel: Denial of Service due to NULL function pointer race in timer shutdown kernel: procfs: avoid fetching build ID while holding VMA lock</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:49871"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rlsa-2026:49871</id>
    <title>RLSA-2026:49871 — Moderate: kernel security, bug fix, and enhancement update</title>
    <updated>2026-10-03T08:42:17.436334+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:10: kernel</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* kernel: Linux kernel: Denial of Service due to NULL function pointer race in timer shutdown (CVE-2025-68214)</p>
<p>* kernel: procfs: avoid fetching build ID while holding VMA lock (CVE-2026-23199)</p>
<p>Bug Fix(es) and Enhancement(s):</p>
<p>* [Lenovo] Graphics not working on T14 G7 Intel (Pantherlake) (JIRA:Rocky Linux-172832)</p>
<p>* Possible regression with FM350GL [rhel-10.2.z] (JIRA:Rocky Linux-184266)</p>
<p>* [10.2 FEAT] CNB102: dpll: sync with upstream (JIRA:Rocky Linux-211011)</p>
<p>* backport make module and modules-core provides use variant [rhel-10.2.z] (JIRA:Rocky Linux-213965)</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rlsa-2026:49871"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23199</id>
    <title>UBUNTU-CVE-2026-23199</title>
    <updated>2026-10-03T08:42:17.436364+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 106 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: procfs: avoid fetching build ID while holding VMA lock Fix PROCMAP_QUERY to fetch optional build ID only after dropping mmap_lock or per-VMA lock, whichever was used to lock VMA under question, to avoid deadlock reported by syzbot:  -&gt; #1 (&amp;mm-&gt;mmap_lock){++++}-{4:4}:         __might_fault+0xed/0x170         _copy_to_iter+0x118/0x1720         copy_page_to_iter+0x12d/0x1e0         filemap_read+0x720/0x10a0         blkdev_read_iter+0x2b5/0x4e0         vfs_read+0x7f4/0xae0         ksys_read+0x12a/0x250         do_syscall_64+0xcb/0xf80         entry_SYSCALL_64_after_hwframe+0x77/0x7f  -&gt; #0 (&amp;sb-&gt;s_type-&gt;i_mutex_key#8){++++}-{4:4}:         __lock_acquire+0x1509/0x26d0         lock_acquire+0x185/0x340         down_read+0x98/0x490         blkdev_read_iter+0x2a7/0x4e0         __kernel_read+0x39a/0xa90         freader_fetch+0x1d5/0xa80         __build_id_parse.isra.0+0xea/0x6a0         do_procmap_query+0xd75/0x1050         procfs_procmap_ioctl+0x7a/0xb0         __x64_sys_ioctl+0x18e/0x210         do_syscall_64+0xcb/0xf80         entry_SYSCALL_64_after_hwframe+0x77/0x7f  other info that might help us debug this:   Possible unsafe locking scenario:         CPU0                    CPU1         ----                    ----    rlock(&amp;mm-&gt;mmap_lock);                                 lock(&amp;sb-&gt;s_type-&gt;i_mutex_key#8);                                 lock(&amp;mm-&gt;mmap_lock);    rlock(&amp;sb-&gt;s_type-&gt;i_mutex_key#8);   *** DEADLOCK *…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23199"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0421</id>
    <title>WID-SEC-W-2026-0421 — Linux Kernel: Mehrere Schwachstellen</title>
    <updated>2026-10-03T08:42:17.436585+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-0421"/>
  </entry>
</feed>
