CVE-2026-45476
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 · uneditedUse after free in Linux MANA Driver allows an authorized attacker to elevate privileges locally.
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 confidenceA use-after-free vulnerability exists in the Linux MANA (Microsoft Azure Network Adapter) driver. This memory corruption bug allows a locally authorized attacker to exploit freed memory and escalate privileges to root by triggering the UAF condition in the kernel driver.
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 dataall versionsCVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify if MANA driver is loadedRun 'lsmod | grep mana' or check '/proc/modules' for the mana driver moduleAffected if The mana or manadev module appears in the loaded modules list
-
Check MANA driver versionRun 'modinfo mana' or inspect '/sys/module/mana/version' if the module is loadedAffected if Any version of the MANA driver is present (all versions are affected)
-
Confirm Azure environment contextCheck for Azure-specific indicators such as 'azure' in dmesg, cloud provider metadata endpoints, or check if running on an Azure VMAffected if The system is running on Microsoft Azure where the MANA driver would be utilized
-
Inspect network adapter configurationRun 'ip link show' or check '/sys/class/net' to identify network interfaces that may be managed by the MANA driverAffected if Network interfaces associated with the MANA driver are present and active
If the MANA driver is loaded on an Azure-based Linux system, the environment is affected since all versions of this driver contain the use-after-free vulnerability.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedUpdate the Linux MANA driver to the patched version provided by the vendor or update the kernel package. Monitor for any available security advisories from the Linux distribution or Microsoft for the specific MANA driver version.
- Check for available Microsoft security updates for Azure Network Adapter by visiting the Microsoft Security Response Center (msrc.microsoft.com) and searching for CVE-2026-45476
- Apply the security update provided by Microsoft for the Linux MANA driver
- Reboot the affected system if required by the security update
- Verify the patch has been applied by checking the driver version or system logs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45476 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45476 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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