Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-57874arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL

Description

In the Linux kernel, the following vulnerability has been resolved: arm64: ptrace: fix partial SETREGSET for NT_ARM_TAGGED_ADDR_CTRL Currently tagged_addr_ctrl_set() doesn't initialize the temporary 'ctrl' variable, and a SETREGSET call with a length of zero will leave this uninitialized. Consequently tagged_addr_ctrl_set() will consume an arbitrary value, potentially leaking up to 64 bits of memory from the kernel stack. The read is limited to a specific slot on the stack, and the issue does not provide a write mechanism. As set_tagged_addr_ctrl() only accepts values where bits [63:4] zero and rejects other values, a partial SETREGSET attempt will randomly succeed or fail depending on the value of the uninitialized value, and the exposure is significantly limited. Fix this by initializing the temporary value before copying the regset from userspace, as for other regsets (e.g. NT_PRSTATUS, NT_PRFPREG, NT_ARM_SYSTEM_CALL). In the case of a zero-length write, the existing value of the tagged address ctrl will be retained. The NT_ARM_TAGGED_ADDR_CTRL regset is only visible in the user_aarch64_view used by a native AArch64 task to manipulate another native AArch64 task. As get_tagged_addr_ctrl() only returns an error value when called for a compat task, tagged_addr_ctrl_get() and tagged_addr_ctrl_set() should never observe an error value from get_tagged_addr_ctrl(). Add a WARN_ON_ONCE() to both to indicate that such an error would be unexpected, and error handlnig is not missing in either case.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 16 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-57874, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium6.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
NVDNVD · Modified3.1Medium6.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.1.

Affected products

  • Linux · Linux

    • affected 2200aa7154cb7ef76bac93e98326883ba64bfa2e – < 1152dd13845efde5554f80c7e1233bae1d26bd3e
    • affected 2200aa7154cb7ef76bac93e98326883ba64bfa2e – < 1c176f5155ee6161fee6f416b64aa50394d3f220
    • affected 2200aa7154cb7ef76bac93e98326883ba64bfa2e – < 1370cf3eb5495d70e00547598583a4cd45b40b99
    • affected 2200aa7154cb7ef76bac93e98326883ba64bfa2e – < 96035c0093db258975b8887676afe59a64c34a72
    • affected 2200aa7154cb7ef76bac93e98326883ba64bfa2e – < abd614bbfcee73247495bd9472da8f85ac83546e
    • affected 2200aa7154cb7ef76bac93e98326883ba64bfa2e – < ca62d90085f4af36de745883faab9f8a7cbb45d3
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.10.231 – ≤ 5.10.*
    • unaffected 5.15.174 – ≤ 5.15.*
    • unaffected 6.1.120 – ≤ 6.1.*
    • unaffected 6.6.66 – ≤ 6.6.*
    • unaffected 6.12.5 – ≤ 6.12.*
    • unaffected 6.13 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-57874 badge
[![CVE-2024-57874](https://cveledger.app/badge/CVE-2024-57874.svg)](https://cveledger.app/cve/CVE-2024-57874)

Record last updated .