Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-50275: arm64/sve: Discard stale CPU state when handling SVE traps

HighCVSS 7.0 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 28/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.24% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 51d11ea0250d6ee461987403bbfd4b2abb5613a7, 51d3d80a6dc314982a9a0aeb0961085922a1aa15, 751ecf6afd6568adc98f2a6052315552c0483d18; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.

Low priority for now. Upgrade to Linux Linux 51d11ea0250d6ee461987403bbfd4b2abb5613a7, 51d3d80a6dc314982a9a0aeb0961085922a1aa15, 751ecf6afd6568adc98f2a6052315552c0483d18; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 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: arm64/sve: Discard stale CPU state when handling SVE traps The logic for handling SVE traps manipulates saved FPSIMD/SVE state incorrectly, and a race with preemption can result in a task having TIF_SVE set and TIF_FOREIGN_FPSTATE clear even though the live CPU state is stale (e.g. with SVE traps enabled). This has been observed to result in warnings from do_sve_acc() where SVE traps are not expected while TIF_SVE is set: | if (test_and_set_thread_flag(TIF_SVE)) | WARN_ON(1); /* SVE access shouldn't have trapped */ Warnings of this form have been reported intermittently, e.g. https://lore.kernel.org/linux-arm-kernel/CA+G9fYtEGe_DhY2Ms7+L7NKsLYUomGsgqpdBj+QwDLeSg=JhGg@mail.gmail.com/ https://lore.kernel.org/linux-arm-kernel/000000000000511e9a060ce5a45c@google.com/ The race can occur when the SVE trap handler is preempted before and after manipulating the saved FPSIMD/SVE state, starting and ending on the same CPU, e.g. | void do_sve_acc(unsigned long esr, struct pt_regs *regs) | { | // Trap on CPU 0 with TIF_SVE clear, SVE traps enabled | // task->fpsimd_cpu is 0. | // per_cpu_ptr(&fpsimd_last_state, 0) is task. | | ... | | // Preempted; migrated from CPU 0 to CPU 1. | // TIF_FOREIGN_FPSTATE is set. | | get_cpu_fpsimd_context(); | | if (test_and_set_thread_flag(TIF_SVE)) | WARN_ON(1); /* SVE access shouldn't have trapped */ | | sve_init_regs() { | if (!test_thread_flag(TIF_FOREIGN_FPSTATE)) { | ... | } else { | fpsimd_to_sve(current); | current->thread.fp_type = FP_STATE_SVE; | } | } | | put_cpu_fpsimd_context(); | | // Preempted; migrated from CPU 1 to CPU 0. | // task->fpsimd_cpu is still 0 | // If per_cpu_ptr(&fpsimd_last_state, 0) is still task then: | // - Stale HW state is reused (with SVE traps enabled) | // - TIF_FOREIGN_FPSTATE is cleared | // - A return to userspace skips HW state restore | } Fix the case where the state is not live and TIF_FOREIGN_FPSTATE is set by calling fpsimd_flush_task_state() to detach from the saved CPU state. This ensures that a subsequent context switch will not reuse the stale CPU state, and will instead set TIF_FOREIGN_FPSTATE, forcing the new state to be reloaded from memory prior to a return to userspace.

Published
Nov 19, 2024
Updated
Oct 15, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.0 / 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.

CNA vs NVD score

NVD
7.0
CNA · Linux
7.3
0.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-2024-50275

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.13affected
    • cccb78ce89c45a4414db712be4986edfb92434bd and later · before 51d3d80a6dc314982a9a0aeb0961085922a1aa15affected · git
    • cccb78ce89c45a4414db712be4986edfb92434bd and later · before de529504b3274d57caf8f66800b714b0d3ee235aaffected · git
    • cccb78ce89c45a4414db712be4986edfb92434bd and later · before 51d11ea0250d6ee461987403bbfd4b2abb5613a7affected · git
    • cccb78ce89c45a4414db712be4986edfb92434bd and later · before fa9ce027b3ce37a2bb173bf2553b5caa438fd8c9affected · git
    • cccb78ce89c45a4414db712be4986edfb92434bd and later · before 751ecf6afd6568adc98f2a6052315552c0483d18affected · git
    • before 5.13not affected · semver
    • 5.15.174 and later · up to and including 5.15.*not affected · semver
    • 6.1.120 and later · up to and including 6.1.*not affected · semver
    • 6.6.61 and later · up to and including 6.6.*not affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.13 and later · before 6.6.61
  • linux linux kernel6.7 and later · before 6.11.8
  • linux linux kernel6.12

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.37.1.el8_104.18.0-553.37.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.37.1.rt7.378.el8_104.18.0-553.37.1.rt7.378.el8_10

+96

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-2024-50297Nov 18, 2024 · net: xilinx: axienet: Enqueue Tx packets in dql before dmaengine starts
    18Monitor
  • ← EarlierCVE-2024-50300Nov 18, 2024 · regulator: rtq2208: Fix uninitialized use of regulator_config
    22Monitor
  • Later →CVE-2024-50285Nov 19, 2024 · ksmbd: check outstanding simultaneous SMB operations
    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 Linux51d11ea0250d6ee461987403bbfd4b2abb5613a7Vendor (CNA)
Linux Linux51d3d80a6dc314982a9a0aeb0961085922a1aa15Vendor (CNA)
Linux Linux751ecf6afd6568adc98f2a6052315552c0483d18Vendor (CNA)
Linux Linuxde529504b3274d57caf8f66800b714b0d3ee235aVendor (CNA)
Linux Linuxfa9ce027b3ce37a2bb173bf2553b5caa438fd8c9Vendor (CNA)
azl3 kernel 6.6.57.1-7 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.64.2-1 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.180.1-1 on CBL-Mariner 2.05.15.176.3-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool7.4.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-503.22.1.el9_5 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.123-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.4.0-503.22.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-503.22.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-503.22.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-503.22.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-503.22.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-503.22.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-503.22.1.el9_5 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+18

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.

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.
  • Special conditions such as timing or configuration are required.

If successful

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

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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