Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68179: s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/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.15% (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 5e23918e4352288323d13fb511116cdea0234b71, 64e2f60f355e556337fcffe80b9bcff1b22c9c42, 7088465f10816d9425b95740b37c95f082041d76.

Low priority for now. Upgrade to Linux Linux 5e23918e4352288323d13fb511116cdea0234b71, 64e2f60f355e556337fcffe80b9bcff1b22c9c42, 7088465f10816d9425b95740b37c95f082041d76 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: s390: Disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP As reported by Luiz Capitulino enabling HVO on s390 leads to reproducible crashes. The problem is that kernel page tables are modified without flushing corresponding TLB entries. Even if it looks like the empty flush_tlb_all() implementation on s390 is the problem, it is actually a different problem: on s390 it is not allowed to replace an active/valid page table entry with another valid page table entry without the detour over an invalid entry. A direct replacement may lead to random crashes and/or data corruption. In order to invalidate an entry special instructions have to be used (e.g. ipte or idte). Alternatively there are also special instructions available which allow to replace a valid entry with a different valid entry (e.g. crdte or cspg). Given that the HVO code currently does not provide the hooks to allow for an implementation which is compliant with the s390 architecture requirements, disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP again, which is basically a revert of the original patch which enabled it.

Published
Dec 16, 2025
Updated
Oct 14, 2026
EPSS
0.1% · 4th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-68179

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • 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, at most 30 a day (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.

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.

—

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.2affected
    • 00a34d5a99c0631bd780b14cbe3813d0b39c3886 and later · before 7088465f10816d9425b95740b37c95f082041d76affected · git
    • 00a34d5a99c0631bd780b14cbe3813d0b39c3886 and later · before 5e23918e4352288323d13fb511116cdea0234b71affected · git
    • 00a34d5a99c0631bd780b14cbe3813d0b39c3886 and later · before d4a8238e5729505b7394ccb007e5dc3e557aa66baffected · git
    • 00a34d5a99c0631bd780b14cbe3813d0b39c3886 and later · before 64e2f60f355e556337fcffe80b9bcff1b22c9c42affected · git
    • before 6.2not affected · semver
    • 6.6.117 and later · up to and including 6.6.*not affected · semver
    • 6.12.58 and later · up to and including 6.12.*not affected · semver
    • 6.17.8 and later · up to and including 6.17.*not affected · semver
    • 6.18 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.12.63-16.12.63-1
Debian:14linuxbefore 6.17.8-16.17.8-1
openSUSE:Leap 16.0dtb-aarch64before 6.12.0-160000.37.16.12.0-160000.37.1
openSUSE:Leap 16.0kernel-64kbbefore 6.12.0-160000.37.16.12.0-160000.37.1
openSUSE:Leap 16.0kernel-azurebefore 6.12.0-160000.37.16.12.0-160000.37.1
openSUSE:Leap 16.0kernel-defaultbefore 6.12.0-160000.37.16.12.0-160000.37.1
openSUSE:Leap 16.0kernel-default-basebefore 6.12.0-160000.37.1.160000.2.196.12.0-160000.37.1.160000.2.19
openSUSE:Leap 16.0kernel-docsbefore 6.12.0-160000.37.16.12.0-160000.37.1
openSUSE:Leap 16.0kernel-kvmsmallbefore 6.12.0-160000.37.16.12.0-160000.37.1
openSUSE:Leap 16.0kernel-obs-buildbefore 6.12.0-160000.37.16.12.0-160000.37.1
openSUSE:Leap 16.0kernel-obs-qabefore 6.12.0-160000.37.16.12.0-160000.37.1
openSUSE:Leap 16.0kernel-rtbefore 6.12.0-160000.37.16.12.0-160000.37.1
openSUSE:Leap 16.0kernel-sourcebefore 6.12.0-160000.37.16.12.0-160000.37.1
openSUSE:Leap 16.0kernel-symsbefore 6.12.0-160000.37.16.12.0-160000.37.1
openSUSE:Leap 16.0kernel-zfcpdumpbefore 6.12.0-160000.37.16.12.0-160000.37.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-defaultbefore 6.4.0-150600.23.135.16.4.0-150600.23.135.1
SUSE:Linux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_31before 1-150600.13.3.41-150600.13.3.4
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7_Update_21before 1-150700.15.3.11-150700.15.3.1
SUSE:Linux Enterprise Live Patching 15 SP7kernel-livepatch-SLE15-SP7-RT_Update_20before 1-150700.1.3.11-150700.1.3.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-64kbbefore 6.4.0-150700.53.81.16.4.0-150700.53.81.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-defaultbefore 6.4.0-150700.53.81.16.4.0-150700.53.81.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-default-basebefore 6.4.0-150700.53.81.1.150700.17.45.16.4.0-150700.53.81.1.150700.17.45.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-sourcebefore 6.4.0-150700.53.81.16.4.0-150700.53.81.1
SUSE:Linux Enterprise Module for Basesystem 15 SP7kernel-zfcpdumpbefore 6.4.0-150700.53.81.16.4.0-150700.53.81.1

+33

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68177Dec 16, 2025 · cpufreq/longhaul: handle NULL policy in longhaul_exit
    0Monitor
  • ← EarlierCVE-2025-68178Dec 16, 2025 · blk-cgroup: fix possible deadlock while configuring policy
    0Monitor
  • Later →CVE-2025-68180Dec 16, 2025 · drm/amd/display: Fix NULL deref in debugfs odm_combine_segments
    0Monitor

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 Linux5e23918e4352288323d13fb511116cdea0234b71Vendor (CNA)
Linux Linux64e2f60f355e556337fcffe80b9bcff1b22c9c42Vendor (CNA)
Linux Linux7088465f10816d9425b95740b37c95f082041d76Vendor (CNA)
Linux Linuxd4a8238e5729505b7394ccb007e5dc3e557aa66bVendor (CNA)
debian:linux6.12.63-1 · Debian:13Package registry (OSV)
opensuse:dtb-aarch646.12.0-160000.37.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-64kb6.12.0-160000.37.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-azure6.12.0-160000.37.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default6.12.0-160000.37.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-default-base6.12.0-160000.37.1.160000.2.19 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-docs6.12.0-160000.37.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-kvmsmall6.12.0-160000.37.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-build6.12.0-160000.37.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-obs-qa6.12.0-160000.37.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-rt6.12.0-160000.37.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-source6.12.0-160000.37.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:kernel-syms6.12.0-160000.37.1 · openSUSE:Leap 16.0Package registry (OSV)
suse:kernel-64kb6.12.0-160000.37.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-azure6.12.0-160000.37.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-default6.12.0-160000.37.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-default-base6.12.0-160000.37.1.160000.2.19 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-docs6.12.0-160000.37.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-kvmsmall6.12.0-160000.37.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-obs-build6.12.0-160000.37.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-obs-qa6.12.0-160000.37.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:kernel-rt6.12.0-160000.37.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-source6.12.0-160000.37.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:kernel-syms6.12.0-160000.37.1 · SUSE:Linux Micro Extras 6.2Package registry (OSV)
suse:kernel-zfcpdump6.12.0-160000.37.1 · SUSE:Linux Enterprise Server 16.0Package 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.

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

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

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

All records