CVE-2025-68231 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
- EPSS
- 0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- NVD analysis
- Deferred: the NVD does not plan to analyze it
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 6.1.159
- Linux Linux: fixed in 6.6.118
- Linux Linux: fixed in 6.12.60
- Linux Linux: fixed in 6.17.10
- Linux Linux: fixed in 6.18
- Debian, Ubuntu, Azure Linux, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2025-68231 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-68231?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-68231?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-68231 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 4.1 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.1 | 6.1.159 |
| Linux | 6.6 | 6.6.118 |
| Linux | 6.12 | 6.12.60 |
| Linux | 6.17 | 6.17.10 |
| Linux | later releases | 6.18 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 11 | linux-6.1 | 6.1.159-1~deb11u1 | DLA-4436-1 |
| Debian | 12 | linux | 6.1.159-1 | DEBIAN-CVE-2025-68231 |
| Debian | 13 | linux | 6.12.63-1 | DEBIAN-CVE-2025-68231 |
| Debian | 14 | linux | 6.17.10-1 | DEBIAN-CVE-2025-68231 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2025-68231 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2025-68231 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2025-68231 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 47 more | no fix listed | UBUNTU-CVE-2025-68231 |
| Ubuntu | 22.04:LTS | linux-aws-6.8 | 6.8.0-1050.53~22.04.1 | UBUNTU-CVE-2025-68231 USN-8095-4 |
| Ubuntu | 22.04:LTS | linux-azure-6.8 | 6.8.0-1051.57~22.04.1 | UBUNTU-CVE-2025-68231 USN-8126-1 |
| Ubuntu | 22.04:LTS | linux-azure-fde-6.8 | 6.8.0-1058.65~22.04.1 | UBUNTU-CVE-2025-68231 |
| Ubuntu | 22.04:LTS | linux-gcp-6.8 | 6.8.0-1052.55~22.04.1 | UBUNTU-CVE-2025-68231 USN-8095-1 |
| Ubuntu | 22.04:LTS | linux-hwe-6.8, linux-riscv-6.8 | 6.8.0-106.106~22.04.1 | UBUNTU-CVE-2025-68231 USN-8095-1 |
| Ubuntu | 22.04:LTS | linux-ibm-6.8 | 6.8.0-1049.49~22.04.1 | UBUNTU-CVE-2025-68231 USN-8095-1 |
| Ubuntu | 22.04:LTS | linux-lowlatency-hwe-6.8 | 6.8.0-106.106.1~22.04.1 | UBUNTU-CVE-2025-68231 USN-8095-1 |
| Ubuntu | 22.04:LTS | linux-nvidia-6.8 | 6.8.0-1049.52~22.04.1 | UBUNTU-CVE-2025-68231 USN-8100-1 |
| 50 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Azure Linux | 3 | kernel | 6.6.119.3-1 | AZL-72458 |
| Alpaquita | 23 | linux-lts | 6.1.159-r0 | BELL-CVE-2025-68231 |
| Alpaquita | 25 | linux-lts | 6.12.61-r0 | BELL-CVE-2025-68231 |
| Alpaquita | stream | linux-lts | 6.18.35-r1 | BELL-CVE-2025-68231 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.
Red Hat
Red Hat rates this Moderate.
HIGHMEM is a 32-bit x86 feature for accessing memory above ~896MB. Modern 64-bit systems don't use HIGHMEM. This affects 32-bit kernels with large memory configurations using mempool poisoning.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Out of support scope | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 8 | kernel-rt | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Fix deferred |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-68231.
References
- https://git.kernel.org/stable/c/19de79aaea33ee1ea058c8711b3b2b4a7e4decd4
- https://git.kernel.org/stable/c/6a13b56537e7b0d97f4bb74e8038ce471f9770d7
- https://git.kernel.org/stable/c/a79e49e1704367b635edad1479db23d7cf1fb71a
- https://git.kernel.org/stable/c/ea4131665107e66ece90e66bcec1a2f1246cbd41
- https://git.kernel.org/stable/c/ec33b59542d96830e3c89845ff833cf7b25ef172