<?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 01:07:08 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-45892</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-45892</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-45892</guid>
    </item>
    <item>
      <title>OESA-2026-2930 — kernel security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-2930</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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;wifi: mac80211: check tdls flag in ieee80211_tdls_oper&lt;/p&gt;
&lt;p&gt;When NL80211_TDLS_ENABLE_LINK is called, the code only checks if the
station exists but not whether it is actually a TDLS station. This
allows the operation to proceed for non-TDLS stations, causing
unintended side effects like modifying channel context and HT
protection before failing.&lt;/p&gt;
&lt;p&gt;Add a check for sta-&amp;amp;gt;sta.tdls early in the ENABLE_LINK case, before
any side effects occur, to ensure the operation is only allowed for
actual TDLS peers.(CVE-2026-43052)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: brcmfmac: validate bsscfg indices in IF events&lt;/p&gt;
&lt;p&gt;brcmf_fweh_handle_if_event() validates the firmware-provided interface
index before it touches drvr-&amp;amp;gt;iflist[], but it still uses the raw
bsscfgidx field as an array index without a matching range check.&lt;/p&gt;
&lt;p&gt;Reject IF events whose bsscfg index does not fit in drvr-&amp;amp;gt;iflist[]
before indexing the interface array.&lt;/p&gt;
&lt;p&gt;[add missing wifi prefix](CVE-2026-43110)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: roccat: fix use-after-free in roccat_report_event&lt;/p&gt;
&lt;p&gt;roccat_report_event() iterates over the device-&amp;amp;gt;readers list without
holding the readers_lock. This allows a concurrent roccat_release() to
remove and free a reader while it&amp;amp;apos;s still being accessed, leading to a
use-after-f…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: 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;wifi: mac80211: check tdls flag in ieee80211_tdls_oper&lt;/p&gt;
&lt;p&gt;When NL80211_TDLS_ENABLE_LINK is called, the code only checks if the
station exists but not whether it is actually a TDLS station. This
allows the operation to proceed for non-TDLS stations, causing
unintended side effects like modifying channel context and HT
protection before failing.&lt;/p&gt;
&lt;p&gt;Add a check for sta-&amp;amp;gt;sta.tdls early in the ENABLE_LINK case, before
any side effects occur, to ensure the operation is only allowed for
actual TDLS peers.(CVE-2026-43052)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;wifi: brcmfmac: validate bsscfg indices in IF events&lt;/p&gt;
&lt;p&gt;brcmf_fweh_handle_if_event() validates the firmware-provided interface
index before it touches drvr-&amp;amp;gt;iflist[], but it still uses the raw
bsscfgidx field as an array index without a matching range check.&lt;/p&gt;
&lt;p&gt;Reject IF events whose bsscfg index does not fit in drvr-&amp;amp;gt;iflist[]
before indexing the interface array.&lt;/p&gt;
&lt;p&gt;[add missing wifi prefix](CVE-2026-43110)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;HID: roccat: fix use-after-free in roccat_report_event&lt;/p&gt;
&lt;p&gt;roccat_report_event() iterates over the device-&amp;amp;gt;readers list without
holding the readers_lock. This allows a concurrent roccat_release() to
remove and free a reader while it&amp;amp;apos;s still being accessed, leading to a
use-after-f…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-2930</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-45892</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-45892</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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: drop extent cache after doing PARTIAL_VALID1 zeroout When splitting an unwritten extent in the middle and converting it to initialized in ext4_split_extent() with the EXT4_EXT_MAY_ZEROOUT and EXT4_EXT_DATA_VALID2 flags set, it could leave a stale unwritten extent. Assume we have an unwritten file and buffered write in the middle of it without dioread_nolock enabled, it will allocate blocks as written extent.        0  A      B  N        [UUUUUUUUUUUU] on-disk extent      U: unwritten extent        [UUUUUUUUUUUU] extent status tree        [--DDDDDDDD--]                     D: valid data           |&amp;lt;-  -&amp;gt;| ----&amp;gt; this range needs to be initialized ext4_split_extent() first try to split this extent at B with EXT4_EXT_DATA_PARTIAL_VALID1 and EXT4_EXT_MAY_ZEROOUT flag set, but ext4_split_extent_at() failed to split this extent due to temporary lack of space. It zeroout B to N and leave the entire extent as unwritten.        0  A      B  N        [UUUUUUUUUUUU] on-disk extent        [UUUUUUUUUUUU] extent status tree        [--DDDDDDDDZZ]                     Z: zeroed data ext4_split_extent() then try to split this extent at A with EXT4_EXT_DATA_VALID2 flag set. This time, it split successfully and leave an written extent from A to N.        0  A      B  N        [UUWWWWWWWWWW] on-disk extent      W: written extent        [UUUUUUUUUUUU] extent status tree        [--DDDDDDDDZZ] Finally ext4_map_create_blocks()…&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 88 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: ext4: drop extent cache after doing PARTIAL_VALID1 zeroout When splitting an unwritten extent in the middle and converting it to initialized in ext4_split_extent() with the EXT4_EXT_MAY_ZEROOUT and EXT4_EXT_DATA_VALID2 flags set, it could leave a stale unwritten extent. Assume we have an unwritten file and buffered write in the middle of it without dioread_nolock enabled, it will allocate blocks as written extent.        0  A      B  N        [UUUUUUUUUUUU] on-disk extent      U: unwritten extent        [UUUUUUUUUUUU] extent status tree        [--DDDDDDDD--]                     D: valid data           |&amp;lt;-  -&amp;gt;| ----&amp;gt; this range needs to be initialized ext4_split_extent() first try to split this extent at B with EXT4_EXT_DATA_PARTIAL_VALID1 and EXT4_EXT_MAY_ZEROOUT flag set, but ext4_split_extent_at() failed to split this extent due to temporary lack of space. It zeroout B to N and leave the entire extent as unwritten.        0  A      B  N        [UUUUUUUUUUUU] on-disk extent        [UUUUUUUUUUUU] extent status tree        [--DDDDDDDDZZ]                     Z: zeroed data ext4_split_extent() then try to split this extent at A with EXT4_EXT_DATA_VALID2 flag set. This time, it split successfully and leave an written extent from A to N.        0  A      B  N        [UUWWWWWWWWWW] on-disk extent      W: written extent        [UUUUUUUUUUUU] extent status tree        [--DDDDDDDDZZ] Finally ext4_map_create_blocks()…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-45892</guid>
    </item>
  </channel>
</rss>
