The 29 October batch carries two CVEs, and CISA added both to the catalog on 28 October 1: CVE-2026-46300 in the Linux kernel, due 31 October, and CVE-2026-41709 in VMware ESX, due 11 November 2. The kernel entry asks for forensic triage 2. CISA cites evidence of active exploitation for each 1. The kernel entry takes the work first because 31 October comes before 11 November.
The kernel entry, due 31 October
CVE-2026-46300 carries a 7.8 on CVSS 3.1, and the vector starts at AV:L, so an attacker needs an account on the box before anything else happens 3. The defect sits in skb_try_coalesce(). The coalescing path attaches paged fragments from one sk_buff to another and drops the SKBFL_SHARED_FRAG marker on the way. The ESP input path checks skb_has_shared_frag() before it decides whether an uncloned nonlinear skb can skip skb_cow_data(). With the marker gone, that check returns false and the AES-GCM decrypt writes into page-cache backed fragments 3.
The kernel record lays out the route in its own scoring notes: splice readable file pages from an unprivileged account, unshare a user and network namespace with unshare -Urn to gain CAP_NET_ADMIN, install an xfrm association, and deliver the packets over loopback 4. The write reaches page cache, so the bytes on disk keep their checksums while the copy the kernel executes changes.
Kernels from 3.9 up to each branch’s fixed build carry the bug; the first unaffected builds are 5.10.257, 5.15.208, 6.1.174, 6.6.141, 6.12.91, 6.18.33 and 7.0.10 4. The fix went into seven stable branches, and the record published on 23 May. A distribution backport wears a package revision rather than an upstream number, so the running build is what answers a host.
Exploit code is public. nu11secur1ty published an exploit on Exploit Database at the end of May that chains this flaw with CVE-2026-43284 and CVE-2026-43500 to poison the page cache for /usr/bin/su, and that post claims near-certain success on the distributions it lists 5. Rapid7 ships a Metasploit module for the kernel bug 6. I cannot check the exploit author’s success rate. The module I can confirm, and it matters because a module turns a memory write primitive into a console session for someone who has never read the patch.
The question I send to the host list asks for the running kernel. A host that took the new package and skipped the reboot still runs the old build, and the 31 October deadline stands regardless of ticket status. The second question is whether IPsec ESP is in play there, because the exploit needs ESP to reach the bug. On my own machines I compare uname -r against the fixed list and read /proc/modules for esp4 and esp6. The same two reads answer a host at work, and the reboot goes to the team that owns it.
The 2.7 that CISA listed anyway
CVE-2026-41709 carries 2.7 on CVSS 3.1, and Broadcom files it in the low range 7. The weakness is CWE-778, insufficient logging. Broadcom’s description runs one line: a malicious administrator can perform certain operations without the host recording them 7. The vector sits at PR:H because the person doing this holds admin rights, and the impact set is C:N/I:L/A:N, which prices a gap in the record as a small integrity problem 8.
CISA listed it on 28 October and set 11 November as the remediation date 2. CISA’s own stakeholder assessment on the record reports exploitation as active, automatable as no, and technical impact as partial 9. That combination describes a bug somebody used with credentials they already held.
Exposure covers ESX 8.0, 9.0.x and 9.1.x, Cloud Foundation 5.x below 5.2.4, vSphere Foundation 9.1.x and 9.0.x, and Telco Cloud 5.0.x and 5.1.x 9. Broadcom published VMSA-2026-0006 on 29 July and last revised it as VMSA-2026-0006.2 on 19 August 7. The fixed column names ESXi80U3j-25429389 for 8.0, ESXi-9.0.2.0100-25595025 for 9.0.x, ESXi-9.1.0.0-25370933 for 9.1.x, and Cloud Foundation 5.2.4 for the 5.x line 7. All four builds have sat in the download portal since July.
A 2.7 measures what one administrator does to a host that account already reaches. An incident responder asks a different question. If someone arrives at a hypervisor on stolen credentials, an action the platform never logged is an action the response team cannot place in a timeline, and a patch does not recover records that were never written. That is why I would put both questions to the platform owner on the same day.
The platform belongs to another team. My part is the deadline and the version list. The detection question travels with it, because a host that keeps its only log copy where the administrator account can reach it hands an intruder the option of leaving no record behind.
What both listings want
Both entries resolve to the same artifact, a host list with a build and an owner next to each name. Neither one settles from a ticket that says patched, and the earlier date does not move for a backlog.
-
Cybersecurity and Infrastructure Security Agency. (2026, October 28). CISA adds two known exploited vulnerabilities to catalog. CISA. https://www.cisa.gov/news-events/alerts/2026/10/28/cisa-adds-two-known-exploited-vulnerabilities-catalog ↩︎ ↩︎
-
Cybersecurity and Infrastructure Security Agency. (2026, October 28). Known exploited vulnerabilities catalog (catalogVersion 2026.10.28). CISA. https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json ↩︎ ↩︎ ↩︎
-
National Vulnerability Database. (2026, May 23). CVE-2026-46300 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-46300 ↩︎ ↩︎
-
CVE Program. (2026, May 23). CVE-2026-46300 record [JSON]. MITRE. https://cveawg.mitre.org/api/cve/CVE-2026-46300 ↩︎ ↩︎
-
nu11secur1ty. (2026, May 29). Linux kernel local privilege escalation (EDB-ID 52591). Exploit Database. https://www.exploit-db.com/exploits/52591 ↩︎
-
Rapid7. (n.d.). Fragnesia LPE (CVE-2026-46300) [Metasploit module]. Rapid7 Vulnerability and Exploit Database. https://www.rapid7.com/db/modules/exploit/linux/local/cve_2026_46300_fragnesia/ ↩︎
-
Broadcom. (2026, August 19). VMSA-2026-0006.2: VMware ESX, vCenter, Workstation, and Fusion updates address multiple vulnerabilities. Broadcom Support Portal. https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017 ↩︎ ↩︎ ↩︎ ↩︎
-
National Vulnerability Database. (2026, July 30). CVE-2026-41709 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2026-41709 ↩︎
-
CVE Program. (2026, July 30). CVE-2026-41709 record [JSON]. MITRE. https://cveawg.mitre.org/api/cve/CVE-2026-41709 ↩︎ ↩︎