CVE-2024-35980: arm64: tlb: Fix TLBI RANGE operand
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.22% (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 944db7b536baaf49d7e576af36a94f4719552b07, ac4ad513de4fba18b4ac0ace132777d0910e8cfa, e3ba51ab24fddef79fc212f9840de54db8fd1685.
- Severity is disputed: the assigning authority (CNA) scores it 8.4, NVD 5.5.
Low priority for now. Upgrade to Linux Linux 944db7b536baaf49d7e576af36a94f4719552b07, ac4ad513de4fba18b4ac0ace132777d0910e8cfa, e3ba51ab24fddef79fc212f9840de54db8fd1685 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: tlb: Fix TLBI RANGE operand KVM/arm64 relies on TLBI RANGE feature to flush TLBs when the dirty pages are collected by VMM and the page table entries become write protected during live migration. Unfortunately, the operand passed to the TLBI RANGE instruction isn't correctly sorted out due to the commit 117940aa6e5f ("KVM: arm64: Define kvm_tlb_flush_vmid_range()"). It leads to crash on the destination VM after live migration because TLBs aren't flushed completely and some of the dirty pages are missed. For example, I have a VM where 8GB memory is assigned, starting from 0x40000000 (1GB). Note that the host has 4KB as the base page size. In the middile of migration, kvm_tlb_flush_vmid_range() is executed to flush TLBs. It passes MAX_TLBI_RANGE_PAGES as the argument to __kvm_tlb_flush_vmid_range() and __flush_s2_tlb_range_op(). SCALE#3 and NUM#31, corresponding to MAX_TLBI_RANGE_PAGES, isn't supported by __TLBI_RANGE_NUM(). In this specific case, -1 has been returned from __TLBI_RANGE_NUM() for SCALE#3/2/1/0 and rejected by the loop in the __flush_tlb_range_op() until the variable @scale underflows and becomes -9, 0xffff708000040000 is set as the operand. The operand is wrong since it's sorted out by __TLBI_VADDR_RANGE() according to invalid @scale and @num. Fix it by extending __TLBI_RANGE_NUM() to support the combination of SCALE#3 and NUM#31. With the changes, [-1 31] instead of [-1 30] can be returned from the macro, meaning the TLBs for 0x200000 pages in the above example can be flushed in one shoot with SCALE#3 and NUM#31. The macro TLBI_RANGE_MASK is dropped since no one uses it any more. The comments are also adjusted accordingly.
- Published
- May 20, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-191
Report tools
Action score
22
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.
CNA vs NVD score
- NVD
- 5.5
- CNA · Linux
- 8.4
- 2.9 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_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
- 6.6affected
- 117940aa6e5f8308f1529e1313660980f1dae771 and later · before ac4ad513de4fba18b4ac0ace132777d0910e8cfaaffected · git
- 117940aa6e5f8308f1529e1313660980f1dae771 and later · before 944db7b536baaf49d7e576af36a94f4719552b07affected · git
- 117940aa6e5f8308f1529e1313660980f1dae771 and later · before e3ba51ab24fddef79fc212f9840de54db8fd1685affected · git
- before 6.6not affected · semver
- 6.6.29 and later · up to and including 6.6.*not affected · semver
- 6.8.7 and later · up to and including 6.8.*not affected · semver
- 6.9 and laternot affected · original_commit_for_fix
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.6 and later · before 6.6.29
- linux linux kernel6.7 and later · before 6.8.7
- linux linux kernel6.9
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.8.9-1 | 6.8.9-1 |
| openSUSE:Leap 15.5 | kernel-azure | before 5.14.21-150500.33.75.1 | 5.14.21-150500.33.75.1 |
| openSUSE:Leap 15.5 | kernel-rt_debug | before 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 |
| openSUSE:Leap 15.5 | kernel-source-azure | before 5.14.21-150500.33.75.1 | 5.14.21-150500.33.75.1 |
| openSUSE:Leap 15.5 | kernel-source-rt | before 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 |
| openSUSE:Leap 15.5 | kernel-syms-azure | before 5.14.21-150500.33.75.1 | 5.14.21-150500.33.75.1 |
| openSUSE:Leap 15.5 | kernel-syms-rt | before 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 |
| openSUSE:Leap 15.6 | kernel-azure | before 6.4.0-150600.8.17.2 | 6.4.0-150600.8.17.2 |
| openSUSE:Leap 15.6 | kernel-rt | before 6.4.0-150600.10.17.1 | 6.4.0-150600.10.17.1 |
| openSUSE:Leap 15.6 | kernel-rt_debug | before 6.4.0-150600.10.17.1 | 6.4.0-150600.10.17.1 |
| openSUSE:Leap 15.6 | kernel-source-azure | before 6.4.0-150600.8.17.1 | 6.4.0-150600.8.17.1 |
| openSUSE:Leap 15.6 | kernel-source-rt | before 6.4.0-150600.10.17.1 | 6.4.0-150600.10.17.1 |
| openSUSE:Leap 15.6 | kernel-syms-azure | before 6.4.0-150600.8.17.1 | 6.4.0-150600.8.17.1 |
| openSUSE:Leap 15.6 | kernel-syms-rt | before 6.4.0-150600.10.17.1 | 6.4.0-150600.10.17.1 |
| openSUSE:Leap Micro 5.5 | kernel-rt | before 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5-RT_Update_23 | before 1-150500.11.3.1 | 1-150500.11.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP6 | kernel-livepatch-SLE15-SP6-RT_Update_5 | before 1-150600.1.3.1 | 1-150600.1.3.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-rt | before 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-source-rt | before 5.14.21-150500.13.79.1 | 5.14.21-150500.13.79.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | kernel-azure | before 5.14.21-150500.33.75.1 | 5.14.21-150500.33.75.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | kernel-source-azure | before 5.14.21-150500.33.75.1 | 5.14.21-150500.33.75.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP5 | kernel-syms-azure | before 5.14.21-150500.33.75.1 | 5.14.21-150500.33.75.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | kernel-azure | before 6.4.0-150600.8.17.2 | 6.4.0-150600.8.17.2 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | kernel-source-azure | before 6.4.0-150600.8.17.1 | 6.4.0-150600.8.17.1 |
+7
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-35977May 20, 2024 · platform/chrome: cros_ec_uart: properly fix race condition18Monitor
- ← EarlierCVE-2024-35979May 20, 2024 · raid1: fix use-after-free for original bio in raid1_write_request()31Monitor
- Later →CVE-2024-35981May 20, 2024 · virtio_net: Do not send RSS key if it is not supported22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 944db7b536baaf49d7e576af36a94f4719552b07 | Vendor (CNA) |
| Linux Linux | ac4ad513de4fba18b4ac0ace132777d0910e8cfa | Vendor (CNA) |
| Linux Linux | e3ba51ab24fddef79fc212f9840de54db8fd1685 | Vendor (CNA) |
| debian:linux | 6.8.9-1 · Debian:13 | Package registry (OSV) |
| opensuse:kernel-azure | 6.4.0-150600.8.17.2 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-rt | 6.4.0-150600.10.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-rt_debug | 6.4.0-150600.10.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source-azure | 6.4.0-150600.8.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-source-rt | 6.4.0-150600.10.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms-azure | 6.4.0-150600.8.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:kernel-syms-rt | 6.4.0-150600.10.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| suse:kernel-azure | 6.4.0-150600.8.17.2 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5-RT_Update_23 | 1-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP6-RT_Update_5 | 1-150600.1.3.1 · SUSE:Linux Enterprise Live Patching 15 SP6 | Package registry (OSV) |
| suse:kernel-rt | 6.4.0-150600.10.17.1 · SUSE:Real Time Module 15 SP6 | Package registry (OSV) |
| suse:kernel-rt_debug | 6.4.0-150600.10.17.1 · SUSE:Real Time Module 15 SP6 | Package registry (OSV) |
| suse:kernel-source-azure | 6.4.0-150600.8.17.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-source-rt | 6.4.0-150600.10.17.1 · SUSE:Real Time Module 15 SP6 | Package registry (OSV) |
| suse:kernel-syms-azure | 6.4.0-150600.8.17.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP6 | Package registry (OSV) |
| suse:kernel-syms-rt | 6.4.0-150600.10.17.1 · SUSE:Real Time Module 15 SP6 | Package 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-2682833 days apartcifs: fix underflow in parse_server_interfaces()37Monitor
- CVE-2024-2691333 days apartdrm/amd/display: Fix dcn35 8k30 Underflow/Corruption Issue31Monitor
- CVE-2024-46759121 days aparthwmon: (adc128d818) Fix underflows seen when writing limit attributes31Monitor
- CVE-2024-53061183 days apartmedia: s5p-jpeg: prevent buffer overflows31Monitor
- CVE-2024-0565126 days apartKernel: cifs filesystem decryption improper input validation remote code execution vulnerability in function receive_encrypted_standard of client30Monitor
- CVE-2022-49278282 days apartremoteproc: Fix count check in rproc_coredump_write()28Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · 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)
CWE-191 · Integer Underflow (Wrap or Wraparound)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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.