Skip to content
Noroxi
CVE-2024-50102· NVD / CVE Program· CNA Linux

x86: fix user address masking non-canonical speculation issue

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 291313693677a345d4f50aae3c68e28b469f601e, 86e6b1547b3d013bc392adf775b89318441403c2.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 291313693677a345d4f50aae3c68e28b469f601e, 86e6b1547b3d013bc392adf775b89318441403c2 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

In the Linux kernel, the following vulnerability has been resolved: x86: fix user address masking non-canonical speculation issue It turns out that AMD has a "Meltdown Lite(tm)" issue with non-canonical accesses in kernel space. And so using just the high bit to decide whether an access is in user space or kernel space ends up with the good old "leak speculative data" if you have the right gadget using the result: CVE-2020-12965 “Transient Execution of Non-Canonical Accesses“ Now, the kernel surrounds the access with a STAC/CLAC pair, and those instructions end up serializing execution on older Zen architectures, which closes the speculation window. But that was true only up until Zen 5, which renames the AC bit [1]. That improves performance of STAC/CLAC a lot, but also means that the speculation window is now open. Note that this affects not just the new address masking, but also the regular valid_user_address() check used by access_ok(), and the asm version of the sign bit check in the get_user() helpers. It does not affect put_user() or clear_user() variants, since there's no speculative result to be used in a gadget for those operations.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Nov 5, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile

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

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
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
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 kernel6.4 and later · before 6.11.6
  • linux linux kernel6.12

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.4affected
    • b19b74bc99b1501a550f4448d04d59b946dc617a and later · before 291313693677a345d4f50aae3c68e28b469f601eaffected · git
    • b19b74bc99b1501a550f4448d04d59b946dc617a and later · before 86e6b1547b3d013bc392adf775b89318441403c2affected · git
    • before 6.4not affected · semver
    • 6.11.6 and later · up to and including 6.11.*not affected · semver
    • 6.12 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:13linuxbefore 6.11.6-16.11.6-1
Red Hat:rhel_eus:9.4::appstreambpftool-debuginfobefore 0:7.3.0-427.88.1.el9_40:7.3.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-debuginfobefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-develbefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-debuginfobefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-develbefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfobefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-develbefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-devel-matchedbefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-rt-debuginfobefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-tools-debuginfobefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-zfcpdump-develbefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4
Red Hat:rhel_eus:9.4::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-427.88.1.el9_40:5.14.0-427.88.1.el9_4

+54

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • 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
  • CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV
    83Now
  • CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV
    77This week
  • CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV
    77This week
  • CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV
    77This week

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 Linux291313693677a345d4f50aae3c68e28b469f601eVendor (CNA)
Linux Linux86e6b1547b3d013bc392adf775b89318441403c2Vendor (CNA)
debian:linux6.11.6-1 · Debian:13Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.88.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

  • CVE-2021-47226168 days apartx86/fpu: Invalidate FPU state after a failed XRSTOR from a user buffer
    28Monitor
  • CVE-2025-39702304 days apartipv6: sr: Fix MAC comparison to be constant-time
    28Monitor
  • CVE-2023-6240275 days apartKernel: marvin vulnerability side-channel leakage in the rsa decryption operation
    26Monitor
  • CVE-2024-0564280 days apartKernel: max page sharing of kernel samepage merging (ksm) may cause memory deduplication
    26Monitor
  • CVE-2024-4767815 days aparticmp: change the order of rate limits
    22Monitor
  • CVE-2022-48730138 days apartdma-buf: heaps: Fix potential spectre v1 gadget
    22Monitor

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

National notice (Türkiye Cybersecurity Directorate / USOM)

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

All national notices →

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
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-203 · Observable Discrepancy

CVSS vector

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

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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (1 more)

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

All records