<?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://127.0.0.1:10001</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>Sat, 21 Nov 2026 02:46:32 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-31503</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-31503</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-31503</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0519 — De multiples vulnérabilités ont été découvertes dans Microsoft Azure Linux. Elles permettent à un attaquant de provoque…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0519</link>
      <description>certfr-2026-avi-0519</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0519</guid>
    </item>
    <item>
      <title>OESA-2026-2493 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-2493</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: Fix recursive locking in __configfs_open_file()&lt;/p&gt;
&lt;p&gt;In flush_write_buffer, &amp;amp;amp;p-&amp;amp;gt;frag_sem is acquired and then the loaded store
function is called, which, here, is target_core_item_dbroot_store().  This
function called filp_open(), following which these functions were called
(in reverse order), according to the call trace:&lt;/p&gt;
&lt;p&gt;down_read
  __configfs_open_file
  do_dentry_open
  vfs_open
  do_open
  path_openat
  do_filp_open
  file_open_name
  filp_open
  target_core_item_dbroot_store
  flush_write_buffer
  configfs_write_iter&lt;/p&gt;
&lt;p&gt;target_core_item_dbroot_store() tries to validate the new file path by
trying to open the file path provided to it; however, in this case, the bug
report shows:&lt;/p&gt;
&lt;p&gt;db_root: not a directory: /sys/kernel/config/target/dbroot&lt;/p&gt;
&lt;p&gt;indicating that the same configfs file was tried to be opened, on which it
is currently working on. Thus, it is trying to acquire frag_sem semaphore
of the same file of which it already holds the semaphore obtained in
flush_write_buffer(), leading to acquiring the semaphore in a nested manner
and a possibility of recursive locking.&lt;/p&gt;
&lt;p&gt;Fix this by modifying target_core_item_dbroot_store() to use kern_path()
instead of filp_open() to avoid opening the file using filesystem-specific
function __configfs_open_file(), and further modifying it to make this fix
compatible.(CVE-2026-23292)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;scsi: target: Fix recursive locking in __configfs_open_file()&lt;/p&gt;
&lt;p&gt;In flush_write_buffer, &amp;amp;amp;p-&amp;amp;gt;frag_sem is acquired and then the loaded store
function is called, which, here, is target_core_item_dbroot_store().  This
function called filp_open(), following which these functions were called
(in reverse order), according to the call trace:&lt;/p&gt;
&lt;p&gt;down_read
  __configfs_open_file
  do_dentry_open
  vfs_open
  do_open
  path_openat
  do_filp_open
  file_open_name
  filp_open
  target_core_item_dbroot_store
  flush_write_buffer
  configfs_write_iter&lt;/p&gt;
&lt;p&gt;target_core_item_dbroot_store() tries to validate the new file path by
trying to open the file path provided to it; however, in this case, the bug
report shows:&lt;/p&gt;
&lt;p&gt;db_root: not a directory: /sys/kernel/config/target/dbroot&lt;/p&gt;
&lt;p&gt;indicating that the same configfs file was tried to be opened, on which it
is currently working on. Thus, it is trying to acquire frag_sem semaphore
of the same file of which it already holds the semaphore obtained in
flush_write_buffer(), leading to acquiring the semaphore in a nested manner
and a possibility of recursive locking.&lt;/p&gt;
&lt;p&gt;Fix this by modifying target_core_item_dbroot_store() to use kern_path()
instead of filp_open() to avoid opening the file using filesystem-specific
function __configfs_open_file(), and further modifying it to make this fix
compatible.(CVE-2026-23292)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-2493</guid>
    </item>
    <item>
      <title>RLSA-2026:64775 — Important: kernel security, bug fix, and enhancement update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:64775</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel-debug-modules, Rocky Linux:10: libperf, Rocky Linux:10: kernel-rt-modules-core, Rocky Linux:10: kernel-tools-debuginfo, Rocky Linux:10: kernel-debug-debuginfo, Rocky Linux:10: libperf-debuginfo, Rocky Linux:10: kernel-debug-modules-extra, Rocky Linux:10: kernel-rt-core, Rocky Linux:10: kernel-tools, Rocky Linux:10: kernel-rt-debug and 80 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: can: bcm: add locking for bcm_op runtime updates (CVE-2025-38004)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: add NULL checks for idev in SRv6 paths (CVE-2026-23442)&lt;/p&gt;
&lt;p&gt;* kernel: udp: Fix wildcard bind conflict check when using hash2 (CVE-2026-31503)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: prevent possible UaF in addrconf_permanent_addr() (CVE-2026-43339)&lt;/p&gt;
&lt;p&gt;* kernel: tcp: call sk_data_ready() after listener migration (CVE-2026-46015)&lt;/p&gt;
&lt;p&gt;* kernel: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;* kernel: flow_dissector: do not dissect PPPoE PFC frames (CVE-2026-46306)&lt;/p&gt;
&lt;p&gt;* kernel: io_uring/poll: fix signed comparison in io_poll_get_ownership() (CVE-2026-52933)&lt;/p&gt;
&lt;p&gt;* kernel: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (CVE-2026-53075)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation (CVE-2026-53277)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: sit: reload inner IPv6 header after GSO offloads (CVE-2026-53228)&lt;/p&gt;
&lt;p&gt;* kernel: net: add pskb_may_pull() to skb_gro_receive_list() (CVE-2026-53235)&lt;/p&gt;
&lt;p&gt;* kernel: net: guard timestamp cmsgs to real error queue skbs (CVE-2026-53223)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: mcast: Fix use-after-free when processing MLD queries (CVE-2026-53275)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: anycast: insert aca into global hash under idev-&amp;gt;lock (CVE-2026-53259)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: free net-&amp;gt;ipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() (CVE-2026-64002)&lt;/p&gt;
&lt;p&gt;*…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: kernel-debug-modules, Rocky Linux:10: libperf, Rocky Linux:10: kernel-rt-modules-core, Rocky Linux:10: kernel-tools-debuginfo, Rocky Linux:10: kernel-debug-debuginfo, Rocky Linux:10: libperf-debuginfo, Rocky Linux:10: kernel-debug-modules-extra, Rocky Linux:10: kernel-rt-core, Rocky Linux:10: kernel-tools, Rocky Linux:10: kernel-rt-debug and 80 more&lt;/p&gt;
&lt;p&gt;The kernel packages contain the Linux kernel, the core of any Linux operating system.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: can: bcm: add locking for bcm_op runtime updates (CVE-2025-38004)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: add NULL checks for idev in SRv6 paths (CVE-2026-23442)&lt;/p&gt;
&lt;p&gt;* kernel: udp: Fix wildcard bind conflict check when using hash2 (CVE-2026-31503)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: prevent possible UaF in addrconf_permanent_addr() (CVE-2026-43339)&lt;/p&gt;
&lt;p&gt;* kernel: tcp: call sk_data_ready() after listener migration (CVE-2026-46015)&lt;/p&gt;
&lt;p&gt;* kernel: inet: RAW sockets using IPPROTO_RAW MUST drop incoming ICMP (CVE-2026-46266)&lt;/p&gt;
&lt;p&gt;* kernel: flow_dissector: do not dissect PPPoE PFC frames (CVE-2026-46306)&lt;/p&gt;
&lt;p&gt;* kernel: io_uring/poll: fix signed comparison in io_poll_get_ownership() (CVE-2026-52933)&lt;/p&gt;
&lt;p&gt;* kernel: ppp: require CAP_NET_ADMIN in target netns for unattached ioctls (CVE-2026-53075)&lt;/p&gt;
&lt;p&gt;* kernel: KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation (CVE-2026-53277)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: sit: reload inner IPv6 header after GSO offloads (CVE-2026-53228)&lt;/p&gt;
&lt;p&gt;* kernel: net: add pskb_may_pull() to skb_gro_receive_list() (CVE-2026-53235)&lt;/p&gt;
&lt;p&gt;* kernel: net: guard timestamp cmsgs to real error queue skbs (CVE-2026-53223)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: mcast: Fix use-after-free when processing MLD queries (CVE-2026-53275)&lt;/p&gt;
&lt;p&gt;* kernel: ipv6: anycast: insert aca into global hash under idev-&amp;gt;lock (CVE-2026-53259)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: free net-&amp;gt;ipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() (CVE-2026-64002)&lt;/p&gt;
&lt;p&gt;*…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rlsa-2026:64775</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31503</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31503</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 234 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: udp: Fix wildcard bind conflict check when using hash2 When binding a udp_sock to a local address and port, UDP uses two hashes (udptable-&amp;gt;hash and udptable-&amp;gt;hash2) for collision detection. The current code switches to &amp;#34;hash2&amp;#34; when hslot-&amp;gt;count &amp;gt; 10. &amp;#34;hash2&amp;#34; is keyed by local address and local port. &amp;#34;hash&amp;#34; is keyed by local port only. The issue can be shown in the following bind sequence (pseudo code): bind(fd1,  &amp;#34;[fd00::1]:8888&amp;#34;) bind(fd2,  &amp;#34;[fd00::2]:8888&amp;#34;) bind(fd3,  &amp;#34;[fd00::3]:8888&amp;#34;) bind(fd4,  &amp;#34;[fd00::4]:8888&amp;#34;) bind(fd5,  &amp;#34;[fd00::5]:8888&amp;#34;) bind(fd6,  &amp;#34;[fd00::6]:8888&amp;#34;) bind(fd7,  &amp;#34;[fd00::7]:8888&amp;#34;) bind(fd8,  &amp;#34;[fd00::8]:8888&amp;#34;) bind(fd9,  &amp;#34;[fd00::9]:8888&amp;#34;) bind(fd10, &amp;#34;[fd00::10]:8888&amp;#34;) /* Correctly return -EADDRINUSE because &amp;#34;hash&amp;#34; is used  * instead of &amp;#34;hash2&amp;#34;. udp_lib_lport_inuse() detects the  * conflict.  */ bind(fail_fd, &amp;#34;[::]:8888&amp;#34;) /* After one more socket is bound to &amp;#34;[fd00::11]:8888&amp;#34;,  * hslot-&amp;gt;count exceeds 10 and &amp;#34;hash2&amp;#34; is used instead.  */ bind(fd11, &amp;#34;[fd00::11]:8888&amp;#34;) bind(fail_fd, &amp;#34;[::]:8888&amp;#34;)      /* succeeds unexpectedly */ The same issue applies to the IPv4 wildcard address &amp;#34;0.0.0.0&amp;#34; and the IPv4-mapped wildcard address &amp;#34;::ffff:0.0.0.0&amp;#34;. For example, if there are existing sockets bound to &amp;#34;192.168.1.[1-11]:8888&amp;#34;, then binding &amp;#34;0.0.0.0:8888&amp;#34; or &amp;#34;[::ffff:0.0.0.0]:8888&amp;#34; can also miss the conflict when hslot-&amp;gt;count &amp;gt; 10. TCP inet_csk_get_port() already has the correct check in inet_use_bhash2…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe and 234 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: udp: Fix wildcard bind conflict check when using hash2 When binding a udp_sock to a local address and port, UDP uses two hashes (udptable-&amp;gt;hash and udptable-&amp;gt;hash2) for collision detection. The current code switches to &amp;#34;hash2&amp;#34; when hslot-&amp;gt;count &amp;gt; 10. &amp;#34;hash2&amp;#34; is keyed by local address and local port. &amp;#34;hash&amp;#34; is keyed by local port only. The issue can be shown in the following bind sequence (pseudo code): bind(fd1,  &amp;#34;[fd00::1]:8888&amp;#34;) bind(fd2,  &amp;#34;[fd00::2]:8888&amp;#34;) bind(fd3,  &amp;#34;[fd00::3]:8888&amp;#34;) bind(fd4,  &amp;#34;[fd00::4]:8888&amp;#34;) bind(fd5,  &amp;#34;[fd00::5]:8888&amp;#34;) bind(fd6,  &amp;#34;[fd00::6]:8888&amp;#34;) bind(fd7,  &amp;#34;[fd00::7]:8888&amp;#34;) bind(fd8,  &amp;#34;[fd00::8]:8888&amp;#34;) bind(fd9,  &amp;#34;[fd00::9]:8888&amp;#34;) bind(fd10, &amp;#34;[fd00::10]:8888&amp;#34;) /* Correctly return -EADDRINUSE because &amp;#34;hash&amp;#34; is used  * instead of &amp;#34;hash2&amp;#34;. udp_lib_lport_inuse() detects the  * conflict.  */ bind(fail_fd, &amp;#34;[::]:8888&amp;#34;) /* After one more socket is bound to &amp;#34;[fd00::11]:8888&amp;#34;,  * hslot-&amp;gt;count exceeds 10 and &amp;#34;hash2&amp;#34; is used instead.  */ bind(fd11, &amp;#34;[fd00::11]:8888&amp;#34;) bind(fail_fd, &amp;#34;[::]:8888&amp;#34;)      /* succeeds unexpectedly */ The same issue applies to the IPv4 wildcard address &amp;#34;0.0.0.0&amp;#34; and the IPv4-mapped wildcard address &amp;#34;::ffff:0.0.0.0&amp;#34;. For example, if there are existing sockets bound to &amp;#34;192.168.1.[1-11]:8888&amp;#34;, then binding &amp;#34;0.0.0.0:8888&amp;#34; or &amp;#34;[::ffff:0.0.0.0]:8888&amp;#34; can also miss the conflict when hslot-&amp;gt;count &amp;gt; 10. TCP inet_csk_get_port() already has the correct check in inet_use_bhash2…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-31503</guid>
    </item>
  </channel>
</rss>
