Linux Kernel: Four Vulnerabilities Disclosed in Single Batch
Key findings • Four Linux kernel vulnerabilities disclosed together on November 10, 2026. • CVE-2026-58801 allows local information disclosure via stale SMMU entries. • CVE-2026-99288 fix…

Key findings
- Four Linux kernel vulnerabilities disclosed together on November 10, 2026.
- CVE-2026-58801 allows local information disclosure via stale SMMU entries.
- CVE-2026-99288 fixes a race condition in TCP established ehash lookups.
- Two Xen-netback vulnerabilities (CVE-2026-99287, CVE-2026-99286) address cleanup and XenBus connection issues.
On November 10, 2026, a batch of four vulnerabilities in the Linux kernel was disclosed, highlighting issues across different subsystems including ARM SMMU, TCP networking, and Xen virtual interfaces. These vulnerabilities, disclosed within a one-hour window, range in impact from local information disclosure to potential network stability concerns.
One of the disclosed vulnerabilities, CVE-2026-58801, resides in the smmu_domain_config_s1 function within arm-smmu-v3.c. A logic error allows for access to stale stream table entries when stream identifiers are reassigned. This could lead to a local information disclosure vulnerability, requiring system execution privileges for exploitation, and does not necessitate user interaction.
Another vulnerability, CVE-2026-99288, addresses a security issue in the TCP established ehash lookups. The fix involves rejecting unhashed sockets during these lookups. The vulnerability arose from lockless ehash lookups where socket caches using SLAB_TYPESAFE_BY_RCU could lead to memory being reused before an RCU reader finished accessing its old address, potentially causing issues after.
The Xen-specific vulnerabilities include CVE-2026-99287 and CVE-2026-99286, both related to the xen-netback component. CVE-2026-99287 corrects an issue where zeroing out sring pointers on unmap was not properly handled during Xenbus connection failures. If xenvif_map_frontend_data_rings() failed after a ring was already mapped, the cleanup path via xenvif_unmap_frontend_data_rings() did not preserve the ring pointers correctly.
CVE-2026-99286, also in xen-netback, addresses a cleanup issue for XenBus connection failures. It ensures that the vif->num_queues is unpublished before synchronize_net is called. This prevents race conditions where readers accessing vif->num_queues under an rcu_read_lock might encounter issues after the vif structure has been modified.
These vulnerabilities were resolved in subsequent kernel releases. Users of the Linux kernel are advised to update to patched versions to mitigate these security risks. The timely disclosure and resolution of these issues underscore the ongoing efforts to maintain the security and stability of the Linux kernel.
This new article provides significant additional detail on CVE-2026-99288, also known as NoisyTCP, which was part of the November 10th disclosure. It highlights the vulnerability's 11-year history, its presence in almost all Linux distributions, and its potential to crash entire servers remotely by exploiting a use-after-free condition in the TCP networking code. The Register also details the exploit's effectiveness against virtual machines and the challenges in patching, alongside suggested workarounds.