dbcve.org
Linux KernelOperating system · Linux

CVE-2026-53346

HIGH · 7.1 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 6.12.94 / 6.18.36 or later.
See remediation →
73/100
Remediation priority · Elevated
Zero-click 7 weeks old

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
In the Linux kernel, the following vulnerability has been resolved: rust: arm64: set uwtable llvm module flag for CONFIG_UNWIND_TABLES Due to a rustc bug [1] the -Cforce-unwind-tables=y flag only emits the uwtable annotation for functions, but not for the module. This means that compiler-generated functions such as 'asan.module_ctor' do not receive the uwtable annotation. When CONFIG_UNWIND_PATCH_PAC_INTO_SCS is enabled, this leads to boot failures because the dwarf information emitted for the kasan constructors is wrong, which causes the SCS boot patching code to patch the constructor in an illegal manner. Specifically, the paciasp instruction is patched, but the autiasp instruction is not. This mismatch leads to a crash when the constructor is called during boot. ================================================================== BUG: KASAN: global-out-of-bounds in do_basic_setup+0x4c/0x90 Read of size 8 at addr ffffffe3cc7eb488 by task swapper/0/1 Specifically the faulting instruction is the (*fn)() to invoke the constructor in do_ctors() of the init/main.c file. Once the fix lands in rustc, this flag can be made conditional on the rustc version. Note that passing the flag on a rustc with the fix present has no effect. [ The fix [1] has landed for Rust 1.98.0 (expected release on 2026-08-20). Thus add a version check as discussed. - Miguel ] [ Adjusted link and comment. - Miguel ]

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 · high confidence

This is a Linux kernel vulnerability on ARM64 where a rustc bug causes the -Cforce-unwind-tables=y flag to emit uwtable annotations only for functions but not at module level. This results in compiler-generated functions like 'asan.module_ctor' missing the uwtable annotation, causing incorrect DWARF debug info. When CONFIG_UNWIND_PATCH_PAC_INTO_SCS is enabled, the SCS boot patching code patches the paciasp instruction but not the matching autiasp instruction, causing a kernel crash (KASAN: global-out-of-bounds) during boot when constructors run.

MitigationAdd a Rust version check in the kernel build system to conditionally apply the -Cforce-unwind-tables=y flag only for rustc versions before 1.98.0, since the underlying rustc bug was fixed in version 1.98.0 (released August 2026). Systems with Rust 1.98.0+ do not need this flag.

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
Linux KernelOperating system
Affected:>= 6.12, < 6.12.94>= 6.13, < 6.18.36>= 6.19, < 7.0.13= 7.1

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
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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. Verify ARM64 architecture
    Check system architecture with 'uname -m' or 'cat /proc/cpuinfo' to confirm 'aarch64'
    Affected if System is not running ARM64 (aarch64) architecture - this vulnerability only affects ARM64
  2. Check kernel version against affected ranges
    Run 'uname -r' or 'cat /proc/version' and compare to: >= 6.12 < 6.12.94; >= 6.13 < 6.18.36; >= 6.19 < 7.0.13; or 7.1
    Affected if Kernel version falls within any of the affected ranges listed
  3. Confirm CONFIG_UNWIND_PATCH_PAC_INTO_SCS is enabled
    Check kernel config with 'cat /boot/config-$(uname -r)' or 'zcat /proc/config.gz' for CONFIG_UNWIND_PATCH_PAC_INTO_SCS=y
    Affected if CONFIG_UNWIND_PATCH_PAC_INTO_SCS is set to 'y' - this is required for the boot crash to occur
  4. Verify Rust support is enabled in the kernel
    Check kernel config for CONFIG_RUST=y or CONFIG_RUST=m
    Affected if Rust is not enabled (CONFIG_RUST not set) - the vulnerable code path requires Rust compiled code with asan.module_ctor
  5. Check rustc version used during kernel build
    If possible, determine the rustc version used to build the kernel (check build logs or rustc --version in build environment)
    Affected if rustc version is below 1.98.0 - versions before this have the bug that causes missing uwtable annotations at module level

A system is affected if it runs an ARM64 kernel version in the affected range with CONFIG_UNWIND_PATCH_PAC_INTO_SCS enabled, has Rust support compiled in, and was built with rustc < 1.98.0, causing a crash during boot when SCS attempts to patch asan.module_ctor.

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.

dbcve · scoped
Upgrade available Upgrade to 6.12.94 / 6.18.36 / 7.0.13 or later
Fixed in 6.12.946.18.367.0.13
Interim mitigation

Add a Rust version check in the kernel build system to conditionally apply the -Cforce-unwind-tables=y flag only for rustc versions before 1.98.0, since the underlying rustc bug was fixed in version 1.98.0 (released August 2026). Systems with Rust 1.98.0+ do not need this flag.

Recommended fix High confidence

6.12.94 (or 6.18.36, 7.0.13, or 7.2 depending on branch)

  1. Identify the current running Linux kernel version using `uname -r`
  2. If the current version is affected (6.12.x where x < 94, 6.13.x where x < 18, 6.14-6.19.x where x < 36, or 7.0.x where x < 13, or 7.1), plan for an upgrade
  3. Upgrade the Linux kernel to version 6.12.94 or later for the 6.12 branch, 6.18.36 or later for the 6.13-6.17 branch, 7.0.13 or later for the 6.18-6.19 branch, or 7.2 or later for the 7.x branch
  4. After kernel upgrade, ensure the system boots normally and verify no KASAN errors occur in dmesg
Caveat Kernel upgrades may introduce changes to drivers or modules; ensure compatibility with userspace and verify custom modules work with the new kernel version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53346 — 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-53346 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