# CVE-2024-50112: x86/lam: Disable ADDRESS_MASKING in most cases

> Attackers could exploit transient execution flaws in Linear Address Masking to read sensitive memory if speculation mitigations are disabled.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Nov 2024
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2024-50112, DEBIAN-CVE-2024-50112, GHSA-562f-24cq-ggcj, ROOT-OS-DEBIAN-11-CVE-2024-50112, ROOT-OS-DEBIAN-12-CVE-2024-50112, ROOT-OS-UBUNTU-2204-CVE-2024-50112, UBUNTU-CVE-2024-50112

## What is CVE-2024-50112?

CVE-2024-50112 is a high-severity vulnerability in Linux kernel, published on 5 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

x86/lam: Disable ADDRESS_MASKING in most cases

Linear Address Masking (LAM) has a weakness related to transient
execution as described in the SLAM paper[1]. Unless Linear Address
Space Separation (LASS) is enabled this weakness may be exploitable.

Until kernel adds support for LASS[2], only allow LAM for COMPILE_TEST,
or when speculation mitigations have been disabled at compile time,
otherwise keep LAM disabled.

There are no processors in market that support LAM yet, so currently
nobody is affected by this issue.

[1] SLAM: https://download.vusec.net/papers/slam_sp24.pdf
[2] LASS: https://lore.kernel.org/lkml/20230609183632.48706-1-alexander.shishkin@linux.intel.com/

[ dhansen: update SPECULATION_MITIGATIONS -> CPU_MITIGATIONS ]

## Which versions are affected by CVE-2024-50112?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-50112?

Apply the vendor's patch.

## Is CVE-2024-50112 being exploited?

There is no known exploitation of CVE-2024-50112 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50112 and fix it if it is affected.

What it is: CVE-2024-50112 is a high-severity vulnerability in Linux kernel, published on 5 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50112 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-50112/ (Markdown: https://insights.sbomify.com/CVE-2024-50112/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-50112
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-50112
- OSV: https://osv.dev/vulnerability/CVE-2024-50112

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-50112/
Summaries are generated and may contain mistakes; the official description above is the record.