<?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 00:34:48 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:95367 — Important: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:95367</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&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: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (CVE-2026-64378)
  * kernel: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (CVE-2026-72222)
  * kernel: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (CVE-2026-72221)
  * kernel: fs/resctrl: Fix use-after-free during unmount (CVE-2026-72080)
  * kernel: sctp: clear new_transport when removing a peer (CVE-2026-74586)
  * kernel: openvswitch: Fix CT limit teardown use-after-free (CVE-2026-89488)
  * kernel: PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers (CVE-2026-90315)
  * kernel: kernel: xfs: Unauthorized data modification via improper file size exchange handling (CVE-2026-98974)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc&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: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (CVE-2026-64378)
  * kernel: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (CVE-2026-72222)
  * kernel: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (CVE-2026-72221)
  * kernel: fs/resctrl: Fix use-after-free during unmount (CVE-2026-72080)
  * kernel: sctp: clear new_transport when removing a peer (CVE-2026-74586)
  * kernel: openvswitch: Fix CT limit teardown use-after-free (CVE-2026-89488)
  * kernel: PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers (CVE-2026-90315)
  * kernel: kernel: xfs: Unauthorized data modification via improper file size exchange handling (CVE-2026-98974)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:95367</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-72222</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-72222</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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: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-72222</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1164 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1164</link>
      <description>certfr-2026-avi-1164</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1164</guid>
    </item>
    <item>
      <title>OESA-2026-3703 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-3703</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;ASoC: qcom: Fix sc7280 lpass potential buffer overflow&lt;/p&gt;
&lt;p&gt;Case values introduced in commit
5f78e1fb7a3e (&amp;amp;quot;ASoC: qcom: Add driver support for audioreach solution&amp;amp;quot;)
cause out of bounds access in arrays of sc7280 driver data (e.g. in case
of RX_CODEC_DMA_RX_0 in sc7280_snd_hw_params()).&lt;/p&gt;
&lt;p&gt;Redefine LPASS_MAX_PORTS to consider the maximum possible port id for
q6dsp as sc7280 driver utilizes some of those values.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37979)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization&lt;/p&gt;
&lt;p&gt;Syzbot reported shift-out-of-bounds exception on MDIO bus initialization.&lt;/p&gt;
&lt;p&gt;The PHY address should be masked to 5 bits (0-31). Without this
mask, invalid PHY addresses could be used, potentially causing issues
with MDIO bus operations.&lt;/p&gt;
&lt;p&gt;Fix this by masking the PHY address with 0x1f (31 decimal) to ensure
it stays within the valid range.(CVE-2025-38736)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl&lt;/p&gt;
&lt;p&gt;When page reassignment was added to af_alg_pull_tsgl the original
loop wasn&amp;amp;apos;t updated so it may try to reassign one more page than
necessary.&lt;/p&gt;
&lt;p&gt;Add the check to the reassignment so that this does not happen.&lt;/p&gt;
&lt;p&gt;Also u…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS-SP1: 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;ASoC: qcom: Fix sc7280 lpass potential buffer overflow&lt;/p&gt;
&lt;p&gt;Case values introduced in commit
5f78e1fb7a3e (&amp;amp;quot;ASoC: qcom: Add driver support for audioreach solution&amp;amp;quot;)
cause out of bounds access in arrays of sc7280 driver data (e.g. in case
of RX_CODEC_DMA_RX_0 in sc7280_snd_hw_params()).&lt;/p&gt;
&lt;p&gt;Redefine LPASS_MAX_PORTS to consider the maximum possible port id for
q6dsp as sc7280 driver utilizes some of those values.&lt;/p&gt;
&lt;p&gt;Found by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-37979)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net: usb: asix_devices: Fix PHY address mask in MDIO bus initialization&lt;/p&gt;
&lt;p&gt;Syzbot reported shift-out-of-bounds exception on MDIO bus initialization.&lt;/p&gt;
&lt;p&gt;The PHY address should be masked to 5 bits (0-31). Without this
mask, invalid PHY addresses could be used, potentially causing issues
with MDIO bus operations.&lt;/p&gt;
&lt;p&gt;Fix this by masking the PHY address with 0x1f (31 decimal) to ensure
it stays within the valid range.(CVE-2025-38736)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;crypto: af_alg - Fix page reassignment overflow in af_alg_pull_tsgl&lt;/p&gt;
&lt;p&gt;When page reassignment was added to af_alg_pull_tsgl the original
loop wasn&amp;amp;apos;t updated so it may try to reassign one more page than
necessary.&lt;/p&gt;
&lt;p&gt;Add the check to the reassignment so that this does not happen.&lt;/p&gt;
&lt;p&gt;Also u…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-3703</guid>
    </item>
    <item>
      <title>RLSA-2026:95367 — Important: kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:95367</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: perf, Rocky Linux:10: kernel-debuginfo, Rocky Linux:10: kernel-tools, Rocky Linux:10: kernel-core, Rocky Linux:10: kernel-debug-debuginfo, Rocky Linux:10: kernel, Rocky Linux:10: kernel-devel-matched, Rocky Linux:10: rv, Rocky Linux:10: libperf, Rocky Linux:10: kernel-debug-core 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: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (CVE-2026-64378)&lt;/p&gt;
&lt;p&gt;* kernel: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (CVE-2026-72222)&lt;/p&gt;
&lt;p&gt;* kernel: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (CVE-2026-72221)&lt;/p&gt;
&lt;p&gt;* kernel: fs/resctrl: Fix use-after-free during unmount (CVE-2026-72080)&lt;/p&gt;
&lt;p&gt;* kernel: sctp: clear new_transport when removing a peer (CVE-2026-74586)&lt;/p&gt;
&lt;p&gt;* kernel: openvswitch: Fix CT limit teardown use-after-free (CVE-2026-89488)&lt;/p&gt;
&lt;p&gt;* kernel: PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers (CVE-2026-90315)&lt;/p&gt;
&lt;p&gt;* kernel: kernel: xfs: Unauthorized data modification via improper file size exchange handling (CVE-2026-98974)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rocky Linux:10: perf, Rocky Linux:10: kernel-debuginfo, Rocky Linux:10: kernel-tools, Rocky Linux:10: kernel-core, Rocky Linux:10: kernel-debug-debuginfo, Rocky Linux:10: kernel, Rocky Linux:10: kernel-devel-matched, Rocky Linux:10: rv, Rocky Linux:10: libperf, Rocky Linux:10: kernel-debug-core 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: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (CVE-2026-64378)&lt;/p&gt;
&lt;p&gt;* kernel: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (CVE-2026-72222)&lt;/p&gt;
&lt;p&gt;* kernel: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (CVE-2026-72221)&lt;/p&gt;
&lt;p&gt;* kernel: fs/resctrl: Fix use-after-free during unmount (CVE-2026-72080)&lt;/p&gt;
&lt;p&gt;* kernel: sctp: clear new_transport when removing a peer (CVE-2026-74586)&lt;/p&gt;
&lt;p&gt;* kernel: openvswitch: Fix CT limit teardown use-after-free (CVE-2026-89488)&lt;/p&gt;
&lt;p&gt;* kernel: PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers (CVE-2026-90315)&lt;/p&gt;
&lt;p&gt;* kernel: kernel: xfs: Unauthorized data modification via improper file size exchange handling (CVE-2026-98974)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rlsa-2026:95367</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72222</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-72222</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback svc_tcp_handshake() stores the raw svc_xprt pointer in tls_handshake_args.ta_data and submits the request through tls_server_hello_x509(). The handshake core takes only sock_hold(req-&amp;gt;hr_sk); nothing references the embedding struct svc_sock that svc_tcp_handshake_done() reaches via container_of(). Two close races leave the in-flight callback writing through a freed svc_sock. svc_sock_free() calls tls_handshake_cancel() and discards its return value: a false return means handshake_complete() has already set HANDSHAKE_F_REQ_COMPLETED but hp_done() may not have finished, yet svc_sock_free() proceeds to kfree(svsk). The cancel-loser fall-through inside svc_tcp_handshake() itself produces the same window: when wait_for_completion_interruptible_timeout() returns &amp;lt;= 0 (timeout or signal) and tls_handshake_cancel() returns false, the function does not drain, returns, and svc_handle_xprt() calls svc_xprt_received(), which clears XPT_BUSY and can drop the last reference. A concurrent close then runs svc_sock_free() while svc_tcp_handshake_done() is still updating xpt_flags and walking svsk-&amp;gt;sk_handshake_done. The corruption surfaces as set_bit/clear_bit RMW into the freed xpt_flags slab slot and as complete_all() walking and writing the freed wait_queue_head_t list embedded in sk_handshake_done -- a slab-corruption primitive, not a benign read. The pa…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback svc_tcp_handshake() stores the raw svc_xprt pointer in tls_handshake_args.ta_data and submits the request through tls_server_hello_x509(). The handshake core takes only sock_hold(req-&amp;gt;hr_sk); nothing references the embedding struct svc_sock that svc_tcp_handshake_done() reaches via container_of(). Two close races leave the in-flight callback writing through a freed svc_sock. svc_sock_free() calls tls_handshake_cancel() and discards its return value: a false return means handshake_complete() has already set HANDSHAKE_F_REQ_COMPLETED but hp_done() may not have finished, yet svc_sock_free() proceeds to kfree(svsk). The cancel-loser fall-through inside svc_tcp_handshake() itself produces the same window: when wait_for_completion_interruptible_timeout() returns &amp;lt;= 0 (timeout or signal) and tls_handshake_cancel() returns false, the function does not drain, returns, and svc_handle_xprt() calls svc_xprt_received(), which clears XPT_BUSY and can drop the last reference. A concurrent close then runs svc_sock_free() while svc_tcp_handshake_done() is still updating xpt_flags and walking svsk-&amp;gt;sk_handshake_done. The corruption surfaces as set_bit/clear_bit RMW into the freed xpt_flags slab slot and as complete_all() walking and writing the freed wait_queue_head_t list embedded in sk_handshake_done -- a slab-corruption primitive, not a benign read. The pa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-72222</guid>
    </item>
  </channel>
</rss>
