Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2021-46961: irqchip/gic-v3: Do not enable irqs when handling spurious interrups

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 3f72d3709f53af72835af7dc8b15ba61611a0e36, 7be4db5c2b59fa77071c93ca4329876fb9777202, a97709f563a078e259bf0861cd259aa60332890a.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 3f72d3709f53af72835af7dc8b15ba61611a0e36, 7be4db5c2b59fa77071c93ca4329876fb9777202, a97709f563a078e259bf0861cd259aa60332890a or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3: Do not enable irqs when handling spurious interrups We triggered the following error while running our 4.19 kernel with the pseudo-NMI patches backported to it: [ 14.816231] ------------[ cut here ]------------ [ 14.816231] kernel BUG at irq.c:99! [ 14.816232] Internal error: Oops - BUG: 0 [#1] SMP [ 14.816232] Process swapper/0 (pid: 0, stack limit = 0x(____ptrval____)) [ 14.816233] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G O 4.19.95.aarch64 #14 [ 14.816233] Hardware name: evb (DT) [ 14.816234] pstate: 80400085 (Nzcv daIf +PAN -UAO) [ 14.816234] pc : asm_nmi_enter+0x94/0x98 [ 14.816235] lr : asm_nmi_enter+0x18/0x98 [ 14.816235] sp : ffff000008003c50 [ 14.816235] pmr_save: 00000070 [ 14.816237] x29: ffff000008003c50 x28: ffff0000095f56c0 [ 14.816238] x27: 0000000000000000 x26: ffff000008004000 [ 14.816239] x25: 00000000015e0000 x24: ffff8008fb916000 [ 14.816240] x23: 0000000020400005 x22: ffff0000080817cc [ 14.816241] x21: ffff000008003da0 x20: 0000000000000060 [ 14.816242] x19: 00000000000003ff x18: ffffffffffffffff [ 14.816243] x17: 0000000000000008 x16: 003d090000000000 [ 14.816244] x15: ffff0000095ea6c8 x14: ffff8008fff5ab40 [ 14.816244] x13: ffff8008fff58b9d x12: 0000000000000000 [ 14.816245] x11: ffff000008c8a200 x10: 000000008e31fca5 [ 14.816246] x9 : ffff000008c8a208 x8 : 000000000000000f [ 14.816247] x7 : 0000000000000004 x6 : ffff8008fff58b9e [ 14.816248] x5 : 0000000000000000 x4 : 0000000080000000 [ 14.816249] x3 : 0000000000000000 x2 : 0000000080000000 [ 14.816250] x1 : 0000000000120000 x0 : ffff0000095f56c0 [ 14.816251] Call trace: [ 14.816251] asm_nmi_enter+0x94/0x98 [ 14.816251] el1_irq+0x8c/0x180 (IRQ C) [ 14.816252] gic_handle_irq+0xbc/0x2e4 [ 14.816252] el1_irq+0xcc/0x180 (IRQ B) [ 14.816253] arch_timer_handler_virt+0x38/0x58 [ 14.816253] handle_percpu_devid_irq+0x90/0x240 [ 14.816253] generic_handle_irq+0x34/0x50 [ 14.816254] __handle_domain_irq+0x68/0xc0 [ 14.816254] gic_handle_irq+0xf8/0x2e4 [ 14.816255] el1_irq+0xcc/0x180 (IRQ A) [ 14.816255] arch_cpu_idle+0x34/0x1c8 [ 14.816255] default_idle_call+0x24/0x44 [ 14.816256] do_idle+0x1d0/0x2c8 [ 14.816256] cpu_startup_entry+0x28/0x30 [ 14.816256] rest_init+0xb8/0xc8 [ 14.816257] start_kernel+0x4c8/0x4f4 [ 14.816257] Code: 940587f1 d5384100 b9401001 36a7fd01 (d4210000) [ 14.816258] Modules linked in: start_dp(O) smeth(O) [ 15.103092] ---[ end trace 701753956cb14aa8 ]--- [ 15.103093] Kernel panic - not syncing: Fatal exception in interrupt [ 15.103099] SMP: stopping secondary CPUs [ 15.103100] Kernel Offset: disabled [ 15.103100] CPU features: 0x36,a2400218 [ 15.103100] Memory Limit: none which is cause by a 'BUG_ON(in_nmi())' in nmi_enter(). From the call trace, we can find three interrupts (noted A, B, C above): interrupt (A) is preempted by (B), which is further interrupted by (C). Subsequent investigations show that (B) results in nmi_enter() being called, but that it actually is a spurious interrupt. Furthermore, interrupts are reenabled in the context of (B), and (C) fires with NMI priority. We end-up with a nested NMI situation, something we definitely do not want to (and cannot) handle. The bug here is that spurious interrupts should never result in any state change, and we should just return to the interrupted context. Moving the handling of spurious interrupts as early as possible in the GICv3 handler fixes this issue. [maz: rewrote commit message, corrected Fixes: tag]

Published
Feb 27, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-46961

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.1affected
    • 3f1f3234bc2db1c16b9818b9a15a5d58ad45251c and later · before e7ea8e46e3b777be26aa855fe07778c415f24926affected · git
    • 3f1f3234bc2db1c16b9818b9a15a5d58ad45251c and later · before 7be4db5c2b59fa77071c93ca4329876fb9777202affected · git
    • 3f1f3234bc2db1c16b9818b9a15a5d58ad45251c and later · before ea817ac1014c04f47885532b55f5d0898deadfbaaffected · git
    • 3f1f3234bc2db1c16b9818b9a15a5d58ad45251c and later · before 3f72d3709f53af72835af7dc8b15ba61611a0e36affected · git
    • 3f1f3234bc2db1c16b9818b9a15a5d58ad45251c and later · before a97709f563a078e259bf0861cd259aa60332890aaffected · git
    • before 5.1not affected · semver
    • 5.4.118 and later · up to and including 5.4.*not affected · semver
    • 5.10.36 and later · up to and including 5.10.*not affected · semver
    • 5.11.20 and later · up to and including 5.11.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.10.38-15.10.38-1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-default-basebefore 5.3.18-150200.24.188.1.150200.9.95.35.3.18-150200.24.188.1.150200.9.95.3
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-docsbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-obs-buildbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-preemptbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-sourcebefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-symsbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise Live Patching 15 SP2kernel-defaultbefore 5.3.18-150200.24.188.15.3.18-150200.24.188.1
SUSE:Linux Enterprise Live Patching 15 SP2kernel-livepatch-SLE15-SP2_Update_47before 1-150200.5.3.31-150200.5.3.3

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2021-46958Feb 27, 2024 · btrfs: fix race between transaction aborts and fsyncs leading to use-after-free
    18Monitor
  • ← EarlierCVE-2021-46960Feb 27, 2024 · cifs: Return correct error code from smb2_get_enc_key
    22Monitor
  • Later →CVE-2021-46962Feb 27, 2024 · mmc: uniphier-sd: Fix a resource leak in the remove function
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux3f72d3709f53af72835af7dc8b15ba61611a0e36Vendor (CNA)
Linux Linux7be4db5c2b59fa77071c93ca4329876fb9777202Vendor (CNA)
Linux Linuxa97709f563a078e259bf0861cd259aa60332890aVendor (CNA)
Linux Linuxe7ea8e46e3b777be26aa855fe07778c415f24926Vendor (CNA)
Linux Linuxea817ac1014c04f47885532b55f5d0898deadfbaVendor (CNA)
debian:linux5.10.38-1 · Debian:12Package registry (OSV)
suse:kernel-default5.3.18-150200.24.188.1 · SUSE:Linux Enterprise Live Patching 15 SP2Package registry (OSV)
suse:kernel-default-base5.3.18-150200.24.188.1.150200.9.95.3 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-docs5.3.18-150200.24.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP2_Update_471-150200.5.3.3 · SUSE:Linux Enterprise Live Patching 15 SP2Package registry (OSV)
suse:kernel-obs-build5.3.18-150200.24.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-preempt5.3.18-150200.24.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-source5.3.18-150200.24.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-syms5.3.18-150200.24.188.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records