Microsoft Discovers 59 Linux Kernel Security Bugs Using AI, Including Flaws Hidden for Over 20 Years
What happened?
Microsoft’s FORGE Lab used an AI-driven scanning system to find 59 security bugs in the Linux kernel. Some of them sat unnoticed for more than 20 years. The work has so far led to 33 assigned CVEs, and Microsoft confirmed working root privilege-escalation exploits for eight of them. The team used a tool with the codename MDASH. It scanned selected kernel areas from late May to mid-June 2026, and a full-time researcher and an intern led the three-month effort. Fixes for 38 of the reports have already been merged into the main Linux kernel. The results add to a busy year for kernel security.
Key details
- Microsoft FORGE Lab used AI tool MDASH to discover 59 Linux kernel security bugs, some hidden for over 20 years.
- MDASH generated 26,502 raw findings in two weeks, reduced to 11,769 candidates after filtering low-confidence claims.
- 33 CVEs assigned so far, 24 rated High or above (CVSS v3.1 ≥ 7.0); eight have confirmed local root privilege escalation exploits tested in lab settings.
- Reported bugs averaged 8.1 years in kernel; three bugs at least 20 years old, oldest CVE-2026-74544 present for at least 21 years.
- Fixing and merging patches takes far longer than finding bugs; 38 fixes merged so far, median 41 days from first patch to mainline release, up to 108 days.
What is affected?
- Linux kernel (multiple subsystems including net/ipv6, net/ipv4, lib/rhashtable, drivers/net, security/keys, net/xfrm)
What should defenders look for?
- CVE-2026-64554 net/ipv6 Use-after-free in bridged IPv6 fragmentation
- CVE-2026-64563 lib/rhashtable Use-after-free in hash-table walks
- CVE-2026-64580 net/ipv6 Refcount underflow in IPv6 IPsec routing
- CVE-2026-74561 net/ipv4 Use-after-free in next-hop replacement
- CVE-2026-74562 net/ipv4 Use-after-free in next-hop replacement
- CVE-2026-89789 drivers/net Use-after-free in GTP tunnel driver
Summarised by SecOraLens from Cyber Security News. Always read the original source before acting. How SecOraLens verifies advisories.
What to do next
Brief your board. Brief your team.
Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.
