dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2026-47335

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Ubuntu Linux 6.8 contains SAUCE patches with a possible NULL pointer dereference in the handling of AppArmor notifications. The bug can be triggered by an unprivileged local user. This can lead to a kernel panic.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Ubuntu Linux 6.8 kernel contains a NULL pointer dereference vulnerability in the AppArmor notification handling code. An unprivileged local user can trigger this bug, causing a kernel panic (denial of service). This is a local privilege escalation/DoS issue in the kernel's AppArmor security module.

MitigationApply the available Ubuntu kernel security patch for CVE-2026-47335. Test thoroughly in a staging environment before production deployment, as kernel updates carry regression risks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ubuntu LinuxOperating system
Affected:= 6.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the running kernel version
    Run `uname -r` to display the currently running kernel release version
    Affected if The version shown is exactly 6.8
  2. Verify Ubuntu version matching CVE scope
    Run `cat /etc/lsb-release` and check the DISTRIB_RELEASE field, or check `hostnamectl` for OS details
    Affected if The system runs Ubuntu Linux version 6.8
  3. Confirm AppArmor is active on the system
    Run `aa-status` or `cat /sys/kernel/security/apparmor/profiles` to see if AppArmor profiles are loaded
    Affected if AppArmor is enabled and loaded (the vulnerability exists in the AppArmor notification code, so it requires AppArmor to be active)
  4. Check AppArmor module loaded state
    Run `lsmod | grep apparmor` to verify the AppArmor kernel module is currently loaded
    Affected if The apparmor module is loaded into the kernel

A system is affected if it runs Ubuntu Linux kernel version 6.8 with AppArmor enabled and loaded, as the NULL pointer dereference occurs in the AppArmor notification handling code when triggered by a local user.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the available Ubuntu kernel security patch for CVE-2026-47335. Test thoroughly in a staging environment before production deployment, as kernel updates carry regression risks.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing6.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,944.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47335 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47335 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data