<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:o:linux:linux_kernel:7.2:rc1:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3olinuxlinux_kernel7.2rc1/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 18 Nov 2026 22:54:30 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3olinuxlinux_kernel7.2rc1/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Linux Kernel: TCP-AO use-after-free in tcp_ao_destroy_sock (CVE-2026-64459)</title><link>https://feed.craftedsignal.io/briefs/2026-11-linux-kernel-tcp-ao-uaf-cve-2026-64459/</link><pubDate>Wed, 18 Nov 2026 22:54:30 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-linux-kernel-tcp-ao-uaf-cve-2026-64459/</guid><description>A use-after-free vulnerability in the Linux kernel TCP-AO implementation allows an unprivileged attacker to trigger kernel-level memory corruption and potential crashes via a race condition during socket connection.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>A use-after-free vulnerability exists in the Linux kernel's TCP-AO (Authentication Option) implementation within <code>tcp_ao_destroy_sock()</code>. The vulnerability stems from the removal of an RCU grace period when freeing TCP-AO info or keys. This enables a race condition where a reader in softirq context may access memory that has already been freed, leading to potential kernel oops, memory disclosure, or control-flow hijacking. An unprivileged user can trigger this flaw by spraying forged TCP-AO segments against a connection attempt.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker sets up a process within a network namespace to create a TCP socket with TCP_MD5SIG and TCP_AO_ADD_KEY.</li>
<li>Attacker initiates a <code>connect()</code> call, placing the socket into <code>TCP_SYN_SENT</code> state and inserting it into the inet ehash.</li>
<li>Attacker triggers <code>tcp_ao_destroy_sock()</code> by forcing a race condition during the connection process.</li>
<li>Concurrently, the attacker uses raw sockets to spray forged TCP-AO segments toward the socket's four-tuple.</li>
<li>The kernel's <code>tcp_v4_rcv()</code> handler, running in softirq context on another CPU, retrieves the socket from the ehash.</li>
<li>The handler attempts to perform an AO lookup using the already-freed <code>tp-&gt;ao_info</code> pointer.</li>
<li>The kernel accesses reclaimed or poison memory, resulting in a general protection fault or kernel panic.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation leads to a kernel crash (kernel oops) or potential arbitrary kernel memory reads and control-flow hijacking. This vulnerability affects unprivileged users who can manipulate local network namespaces to trigger the race condition.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Upgrade the Linux kernel to a patched version. Based on the advisory, versions 6.18.39, 7.1.4, and 7.2 (or later) contain the fix by restoring the RCU grace period via <code>call_rcu()</code> in <code>tcp_ao_destroy_sock()</code>.</p>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category></item><item><title>Linux Kernel: Bluetooth bpa10x Out-of-Bounds Read (CVE-2026-64549)</title><link>https://feed.craftedsignal.io/briefs/2026-11-linux-bluetooth-oob-read-cve-2026-64549/</link><pubDate>Tue, 17 Nov 2026 22:01:52 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-linux-bluetooth-oob-read-cve-2026-64549/</guid><description>An out-of-bounds read vulnerability in the Linux kernel bpa10x Bluetooth driver allows for potential information exposure of kernel slab memory via system logs and debugfs due to insufficient length validation in bpa10x_setup().</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>An out-of-bounds (OOB) read vulnerability exists in the <code>bpa10x_setup()</code> function within the Linux kernel Bluetooth driver. When the driver sends vendor command 0xfc0e, it processes the response string starting at <code>skb-&gt;data + 1</code> without validating the payload length. A device returning a short or non-NUL-terminated response causes the driver to read adjacent slab memory until a NUL character is encountered.</p>
<h2 id="attack-chain">Attack Chain</h2>
<p>If a Bluetooth device returns a one-byte response or an unterminated payload, the <code>bpa10x_setup()</code> function reads past the end of the data. This data is output to the kernel log via <code>bt_dev_info()</code> and recorded in the <code>firmware-info</code> debugfs file.</p>
<h2 id="impact">Impact</h2>
<p>This vulnerability may lead to the exposure of sensitive kernel slab memory contents within system logs and debugfs files.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Upgrade to a non-affected kernel version. The vulnerability is addressed by implementing a bounded <code>%.*s</code> print format limited to <code>skb-&gt;len - 1</code>, ensuring the driver does not read past the received data. Affected versions include branches &gt;= 4.4, &lt; 5.10.261; &gt;= 5.11, &lt; 5.15.212; &gt;= 5.16, &lt; 6.1.178; &gt;= 6.2, &lt; 6.6.145; &gt;= 6.7, &lt; 6.12.97; &gt;= 6.13, &lt; 6.18.40; &gt;= 6.19, &lt; 7.1.5.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve</category><category>linux</category><category>kernel</category><category>bluetooth</category><category>memory-safety</category></item><item><title>Linux Kernel: KVM arm64 privilege escalation in MOPS handling (CVE-2026-64555)</title><link>https://feed.craftedsignal.io/briefs/2026-11-linux-kvm-mops-cve-2026-64555/</link><pubDate>Tue, 17 Nov 2026 19:50:03 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-linux-kvm-mops-cve-2026-64555/</guid><description>A vulnerability in the Linux kernel KVM implementation for arm64 allows an attacker within a nested-capable KVM guest to trigger improper SPSR_EL2 state handling, potentially leading to host-level privilege escalation or a hypervisor panic.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>A vulnerability exists in the Linux kernel KVM for arm64 systems within the kvm_hyp_handle_mops() function. The issue arises from incorrect handling of synthetic vcpu_cpsr() state during MOPS (Memory Operations) exception rewinding. Under nested virtualization, the kernel fails to translate the synthetic state before writing it to hardware, leading to corruption of hardware SPSR_EL2 registers.</p>
<h2 id="attack-chain">Attack Chain</h2>
<p>The attacker must be executing code inside a KVM/arm64 guest. A guest hypervisor at vEL2 can trigger the MOPS exception by executing a main/epilogue MOPS instruction with ill-formed alignment/size parameters. This occurs during normal vCPU execution without host-side interaction.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows a low-privileged guest user to gain execution at EL2, granting access to the entire host kernel address space and the memory of other guests. Triggering the flaw can also cause a host-wide hypervisor panic, resulting in a denial-of-service for all hosted virtual machines.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Users should apply patches for the following affected version ranges: Linux kernel &gt;= 6.7, &lt; 6.12.97; &gt;= 6.13, &lt; 6.18.40; and &gt;= 6.19, &lt; 7.1.5.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>KVM</category><category>arm64</category><category>privilege-escalation</category><category>linux-kernel</category></item><item><title>Linux kernel rtl8723bs driver out-of-bounds read (CVE-2026-64536)</title><link>https://feed.craftedsignal.io/briefs/2026-11-linux-kernel-rtl8723bs-oob-read-cve-2026-64536/</link><pubDate>Mon, 16 Nov 2026 16:16:27 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-linux-kernel-rtl8723bs-oob-read-cve-2026-64536/</guid><description>A vulnerability in the Linux kernel rtl8723bs wireless driver allows a nearby attacker to trigger out-of-bounds memory reads via malformed information elements during WiFi association, potentially resulting in kernel crashes or information disclosure.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>The Linux kernel rtl8723bs driver contains an out-of-bounds read vulnerability in the <code>is_ap_in_tkip()</code> function. The flaw occurs because the function fails to verify that sufficient bytes remain in the buffer before dereferencing information element (IE) headers and payloads. A nearby attacker can exploit this by transmitting malicious beacon or probe-response frames to a vulnerable host, causing the kernel to read beyond the intended buffer boundaries. This issue was addressed in kernel releases 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, and 7.1.4.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation can result in kernel panics (oops), leading to denial of service, or the potential disclosure of adjacent kernel memory. The vulnerability is triggered during the association path, before authentication credentials are verified, allowing an unprivileged, nearby attacker to trigger the issue against susceptible devices.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update the Linux kernel to the following fixed versions (or later) depending on the release branch: 5.15.212, 6.1.178, 6.6.145, 6.12.96, 6.18.39, or 7.1.4.</li>
<li>If patching is not immediately feasible, restrict the use of devices employing the <code>rtl8723bs</code> driver in untrusted wireless environments.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category></item><item><title>Linux Kernel: Memory corruption in perf event groups (CVE-2026-64556)</title><link>https://feed.craftedsignal.io/briefs/2026-11-linux-perf-cve-2026-64556/</link><pubDate>Sun, 15 Nov 2026 15:27:27 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-linux-perf-cve-2026-64556/</guid><description>A vulnerability in the Linux kernel perf subsystem allows a local unprivileged user to trigger kernel heap memory corruption by creating an inconsistent group state during remove_on_exec operations.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>A memory corruption vulnerability exists in the Linux kernel's perf subsystem regarding the handling of group relationships during <code>remove_on_exec</code> operations. When a leader event is removed while siblings remain, the group state can become inconsistent. A subsequent <code>close</code> operation on the removed leader can lead to a <code>list_add</code> double-add to the PMU context active list, resulting in kernel heap corruption.</p>
<h2 id="attack-chain">Attack Chain</h2>
<p>The vulnerability is triggered locally by an unprivileged user through the use of <code>perf_event_open(2)</code> to build an event group with mixed <code>remove_on_exec</code> flags, followed by <code>execve(2)</code> and <code>close(2)</code> to trigger the corruption. The issue involves pointer manipulation of heap-embedded list nodes.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation results in kernel memory corruption. This can lead to a kernel crash (denial of service), information disclosure through reading adjacent kernel memory, or arbitrary modification of heap objects.</p>
<h2 id="recommendation">Recommendation</h2>
<p>Users should update to a kernel version containing the fix. Affected ranges include Linux kernel versions &gt;= 5.13, &lt; 6.1.191; &gt;= 6.2, &lt; 6.6.145; &gt;= 6.7, &lt; 6.12.96; &gt;= 6.13, &lt; 6.18.39; and &gt;= 6.19, &lt; 7.1.4. Users should verify their distribution's security advisories for specific patch availability.</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve-2026-64556</category><category>linux</category><category>kernel</category><category>perf</category></item><item><title>Linux Kernel: KVM nested VMX use-after-free (CVE-2026-64562)</title><link>https://feed.craftedsignal.io/briefs/2026-08-kvm-vmcs-vulnerability/</link><pubDate>Sun, 09 Aug 2026 09:35:21 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-08-kvm-vmcs-vulnerability/</guid><description>A use-after-free vulnerability in the Linux kernel KVM nested VMX implementation allows a local attacker with nested VMX access to trigger memory corruption via a race condition during vCPU migration.</description><content:encoded><![CDATA[<h2 id="overview">Overview</h2>
<p>A vulnerability exists in the KVM nested VMX implementation within the Linux kernel where a shadow VMCS is prematurely freed while the <code>vmcs01</code> structure maintains a dangling reference to it. During vCPU migration, an asynchronous race condition occurs where the kernel may attempt to execute <code>VMCLEAR</code> on the already freed shadow VMCS memory. This results in a use-after-free (UAF) condition that can lead to host kernel memory corruption, arbitrary information disclosure, or system panics.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows an attacker to compromise the guest-to-host isolation boundary. Observed impacts include potential arbitrary information disclosure, host kernel heap corruption, and host system unavailability via kernel panic. The vulnerability is reachable by local users who have access to <code>/dev/kvm</code> and are permitted to utilize nested VMX features.</p>
<h2 id="recommendation">Recommendation</h2>
<ol>
<li>Identify all Linux systems running KVM with nested virtualization enabled.</li>
<li>Apply the relevant patches for the affected kernel versions:</li>
</ol>
<ul>
<li>5.10.x: Upgrade to 5.10.265 or later</li>
<li>5.15.x: Upgrade to 5.15.216 or later</li>
<li>6.1.x: Upgrade to 6.1.183 or later</li>
<li>6.6.x: Upgrade to 6.6.148 or later</li>
<li>6.12.x: Upgrade to 6.12.101 or later</li>
<li>6.18.x: Upgrade to 6.18.42 or later</li>
<li>7.1.x: Upgrade to 7.1.6 or later</li>
</ul>
<ol start="3">
<li>Restrict access to <code>/dev/kvm</code> and nested virtualization capabilities to only trusted users or service accounts to mitigate the attack vector.</li>
</ol>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>vulnerability</category><category>virtualization</category><category>linux</category><category>kernel</category><category>denial-of-service</category><category>kernel-security</category></item></channel></rss>