Skip to content
major vulnerability· requires attention

Kernel privilege escalation in largepage handling affects Linux kernels used broadly; can lead to root compromise and warrants org-wide attention.

Systems

CVE-2026-49428

8.4
High
EPSS 0.29%Patch availableAug 20, 2026

Local kernel use-after-free in largepage handling allows privilege escalation

common questions

Is CVE-2026-49428 being exploited?

Not confirmed. CVE-2026-49428 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-49428?

CVE-2026-49428 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-49428?

Yes. A fix has been recorded for CVE-2026-49428. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-49428 affect?

CVE-2026-49428 affects Linux kernel (largepage support), Major Linux distributions (Ubuntu, Debian, RHEL, SUSE, etc.). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-49428?

Apply vendor kernel updates when released; restrict untrusted local access and monitor logs

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (largepage support)Major Linux distributions (Ubuntu, Debian, RHEL, SUSE, etc.)
impact

Local attacker can trigger a use-after-free to read freed kernel memory and escalate privileges to root/kernel.

action required

Immediate action required

affected versions
FreeBSD FreeBSD
  • affected>= 15.1-RELEASE and < p1
  • affected>= 15.0-RELEASE and < p11
  • affected>= 14.4-RELEASE and < p7
  • affected>= 14.3-RELEASE and < p16

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free