Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-71102: scs: fix a wrong parameter in __scs_magic

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.14% (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 062774439d442882b44f5eab8c256ad3423ef284, 08bd4c46d5e63b78e77f2605283874bbe868ab19, 1727e8bd69103a68963a5613a0ddb6d8d37df5d3.

Low priority for now. Upgrade to Linux Linux 062774439d442882b44f5eab8c256ad3423ef284, 08bd4c46d5e63b78e77f2605283874bbe868ab19, 1727e8bd69103a68963a5613a0ddb6d8d37df5d3 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: scs: fix a wrong parameter in __scs_magic __scs_magic() needs a 'void *' variable, but a 'struct task_struct *' is given. 'task_scs(tsk)' is the starting address of the task's shadow call stack, and '__scs_magic(task_scs(tsk))' is the end address of the task's shadow call stack. Here should be '__scs_magic(task_scs(tsk))'. The user-visible effect of this bug is that when CONFIG_DEBUG_STACK_USAGE is enabled, the shadow call stack usage checking function (scs_check_usage) would scan an incorrect memory range. This could lead 1. **Inaccurate stack usage reporting**: The function would calculate wrong usage statistics for the shadow call stack, potentially showing incorrect value in kmsg. 2. **Potential kernel crash**: If the value of __scs_magic(tsk)is greater than that of __scs_magic(task_scs(tsk)), the for loop may access unmapped memory, potentially causing a kernel panic. However, this scenario is unlikely because task_struct is allocated via the slab allocator (which typically returns lower addresses), while the shadow call stack returned by task_scs(tsk) is allocated via vmalloc(which typically returns higher addresses). However, since this is purely a debugging feature (CONFIG_DEBUG_STACK_USAGE), normal production systems should be not unaffected. The bug only impacts developers and testers who are actively debugging stack usage with this configuration enabled.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jan 14, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 3th 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.1%

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-2025-71102

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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

Affected versions

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

  • linux linux kernel5.8.1 and later · before 5.10.248
  • linux linux kernel5.11 and later · before 5.15.198
  • linux linux kernel5.16 and later · before 6.1.160
  • linux linux kernel6.2 and later · before 6.6.120
  • linux linux kernel6.7 and later · before 6.12.64
  • linux linux kernel6.13 and later · before 6.18.3
  • linux linux kernel5.8
  • linux linux kernel6.19

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.8affected
    • 5bbaf9d1fcb9be696ee9a61636ab6803556c70f2 and later · before 1727e8bd69103a68963a5613a0ddb6d8d37df5d3affected · git
    • 5bbaf9d1fcb9be696ee9a61636ab6803556c70f2 and later · before cfdf6250b63b953b1d8e60814c8ca96c6f9d1c8caffected · git
    • 5bbaf9d1fcb9be696ee9a61636ab6803556c70f2 and later · before 57ba40b001be27786d0570dd292289df748b306baffected · git
    • 5bbaf9d1fcb9be696ee9a61636ab6803556c70f2 and later · before 062774439d442882b44f5eab8c256ad3423ef284affected · git
    • 5bbaf9d1fcb9be696ee9a61636ab6803556c70f2 and later · before 9ef28943471a16e4f9646bc3e8e2de148e7d8d7baffected · git
    • 5bbaf9d1fcb9be696ee9a61636ab6803556c70f2 and later · before a19fb3611e4c06624fc0f83ef19f4fb8d57d4751affected · git
    • 5bbaf9d1fcb9be696ee9a61636ab6803556c70f2 and later · before 08bd4c46d5e63b78e77f2605283874bbe868ab19affected · git
    • before 5.8not affected · semver
    • 5.10.248 and later · up to and including 5.10.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.3-16.18.3-1

Same product

linux: all records

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-2025-71099Jan 13, 2026 · drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()
    31Monitor
  • ← EarlierCVE-2025-71100Jan 13, 2026 · wifi: rtlwifi: 8192cu: fix tid out of range in rtl92cu_tx_fill_desc()
    31Monitor
  • Later →CVE-2025-71103Jan 14, 2026 · drm/msm: adreno: fix deferencing ifpc_reglist when not declared
    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 Linux062774439d442882b44f5eab8c256ad3423ef284Vendor (CNA)
Linux Linux08bd4c46d5e63b78e77f2605283874bbe868ab19Vendor (CNA)
Linux Linux1727e8bd69103a68963a5613a0ddb6d8d37df5d3Vendor (CNA)
Linux Linux57ba40b001be27786d0570dd292289df748b306bVendor (CNA)
Linux Linux9ef28943471a16e4f9646bc3e8e2de148e7d8d7bVendor (CNA)
Linux Linuxa19fb3611e4c06624fc0f83ef19f4fb8d57d4751Vendor (CNA)
Linux Linuxcfdf6250b63b953b1d8e60814c8ca96c6f9d1c8cVendor (CNA)
debian:linux6.1.162-1 · Debian:12Package 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records