VulnerabilityPublished 18 Oct 2026

CVE-2026-98475: Linux kernel · s390/cmf: Fix virtual vs physical address confusion

Source GCVE Database

Authoritative record:CVE-2026-98475· Medium

Not known to be exploited · fixed in f4d04425e66af2ecee9d1a49ae0484436f3c2fd1 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in f4d04425e66af2ecee9d1a49ae0484436f3c2fd1, b11f369be31ea11c746833e4d3ad51dcd6b5fa2b, 748ec2f7f5df9b4fc742546a8bfc8aa5d847353e +1

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-p4wm-c7q2-mpq9

What to do

Upgrade Linux kernel to f4d04425e66af2ecee9d1a49ae0484436f3c2fd1, b11f369be31ea11c746833e4d3ad51dcd6b5fa2b, 748ec2f7f5df9b4fc742546a8bfc8aa5d847353e or 7f78226eb743b362f52b212d7763801642539d1c.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 14edd0d73bfef320fd5be11495687ba537aa6341, < f4d04425e66af2ecee9d1a49ae0484436f3c2fd1	Fixed in f4d04425e66af2ecee9d1a49ae0484436f3c2fd1
LinuxLinux	Affected ≥ 14edd0d73bfef320fd5be11495687ba537aa6341, < b11f369be31ea11c746833e4d3ad51dcd6b5fa2b	Fixed in b11f369be31ea11c746833e4d3ad51dcd6b5fa2b
LinuxLinux	Affected ≥ 14edd0d73bfef320fd5be11495687ba537aa6341, < 748ec2f7f5df9b4fc742546a8bfc8aa5d847353e	Fixed in 748ec2f7f5df9b4fc742546a8bfc8aa5d847353e
LinuxLinux	Affected ≥ 14edd0d73bfef320fd5be11495687ba537aa6341, < 7f78226eb743b362f52b212d7763801642539d1c	Fixed in 7f78226eb743b362f52b212d7763801642539d1c
LinuxLinux	Affected =6.9	Fixed in–

AI-suggested

A fix has been applied in the Linux kernel source to correct the address confusion issue. Users should update to the fixed kernel version once available. Since this is a kernel-level fix, applying the official kernel update from the vendor or distribution is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should check the vendor advisory or kernel release notes for the exact fixed version and update accordingly.

Description

A vulnerability in the Linux kernel s390 architecture involving confusion between virtual and physical addresses has been fixed. The issue related to the measurement block address being treated incorrectly, causing firmware to use wrong addresses when storing extended format channel measurement data on kernels built with CONFIG_RANDOMIZE_IDENTITY_BASE=y. The fix involves defining certain fields as dma64_t and adding the missing virt_to_dma64() translation to ensure correct address usage.

References

Community reviews

Loading reviews…