BlackTreeIndependent security intelligence

Full vulnerability report · 2025

CVE-2025-38451High confidence

md/md-bitmap: fix GPF in bitmap_get_stats()

Linux · Linux

5.5MediumCVSS 3.1

Recommended action

Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

12 package states

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu release	Source package	Vendor state	Fixed version	Evidence
Ubuntu 24.04 LTSnoble · standard archive	`linux-aws-6.14`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-fde-6.14`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-azure-nvidia-6.14`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-gcp-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-hwe-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-lowlatency-hwe-6.11`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oem-6.14`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-oracle-6.14`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-raspi-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-realtime`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archive	`linux-riscv`	Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.	`Not published in this feed`	Canonical record ↗Source updated 9 Sept 2026

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current

SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5

5 known affected

The vendor explicitly identifies these products as affected by this CVE.

SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.5
SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5

Summary: In the Linux kernel, the following vulnerability has been resolved: md/md-bitmap: fix GPF in bitmap_get_stats() The commit message of commit 6ec1f0239485 ("md/md-bitmap: fix stats collection for external bitmaps") states: Remove the external bitmap check as the statistics should be available regardless of bitmap storage location. Return -EINVAL only for invalid bitmap with no storage (neither in superblock nor in external file). But, the code does not adhere to the above, as it does only check for a valid super-block for "internal" bitmaps. Hence, we observe: Oops: GPF, probably for non-canonical address 0x1cd66f1f40000028 RIP: 0010:bitmap_get_stats+0x45/0xd0 Call Trace: seq_read_iter+0x2b9/0x46a seq_read+0x12f/0x180 proc_reg_read+0x57/0xb0 vfs_read+0xf6/0x380 ksys_read+0x6d/0xf0 do_syscall_64+0x8c/0x1b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e We fix this by checking the existence of a super-block for both the internal and external case.
Remediation: Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current

ENISA EUVD identifier

EUVD-2025-22690

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state: Present in the current official mapping
Known exploitation: Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score: Not supplied in the stored EUVD record
Advisory evidence: No linked advisory details stored yet

Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available

What, why and how

In the Linux kernel, the following vulnerability has been resolved: md/md-bitmap: fix GPF in bitmap_get_stats() The commit message of commit 6ec1f0239485 ("md/md-bitmap: fix stats collection for external bitmaps") states: Remove the external bitmap check as the statistics should be available regardless of bitmap storage location. Return -EINVAL only for invalid bitmap with no storage (neither in superblock nor in external file). But, the code does not adhere to the above, as it does only check for a valid super-block for "internal" bitmaps. Hence, we observe: Oops: GPF, probably for non-canonical address 0x1cd66f1f40000028 RIP: 0010:bitmap_get_stats+0x45/0xd0 Call Trace: seq_read_iter+0x2b9/0x46a seq_read+0x12f/0x180 proc_reg_read+0x57/0xb0 vfs_read+0xf6/0x380 ksys_read+0x6d/0xf0 do_syscall_64+0x8c/0x1b0 entry_SYSCALL_64_after_hwframe+0x76/0x7e We fix this by checking the existence of a super-block for both the internal and external case.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: local access → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Local
Privileges required: Low: a basic authenticated account is required
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration.: CWE not yet assigned
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2025-22690Official EUVD mapping

0 linked advisory records.

Official EUVD record

BSI · German · WID-SEC-W-2025-1653Linux Kernel: Mehrere Schwachstellen

Ein entfernter anonymer Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder andere nicht spezifizierte Angriffe durchzuführen.

Official advisory

CERT-FR · French · CERTFR-2025-AVI-1135Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2025-38440 Référence CVE CVE-2025-38441 https://www.cve.org/CVERecord?id=CVE-2025-38441 Référence CVE CVE-2025-38443 https://www.cve.org/CVERecord?id=CVE-2025-38443 Référence CVE CVE-2025-38444 https://www.cve.org/CVERecord?id=CVE-2025-38444 Référence CVE CVE-2025-38445 https://www.cve.org/CVERecord?id=CVE-2025-38445 Référence CVE CVE-2025-38446 https://www.cve.org/CVERecord?id=CVE-2025-38446 Référence CVE CVE-2025-38448 https://www.cve.org/CVERecord?id=CVE-2025-38448 Référence CVE CVE-2025-38449 https://www.cve.org/CVERecord?id=CVE-2025-38449 Référence CVE CVE-2025-38450 https://www.cve.org/CVERecord?id=CVE-2025-38450 Référence CVE CVE-2025-38451 https://www.cve.org/CVERecord?id=CVE-2025-38451 Référence CVE CVE-2025-38452 https://www.cve.org/CVERecord?id=CVE-2025-38452 Référence CVE CVE-2025-38453 https://www.cve.org/CVERecord?id=CVE-2025-38453 Référence CVE CVE-2025-38454 https://www.cve.org/CVERecord?id=CVE-2025-38454 Référence CVE CVE-2025-38455 https://www.cve.org/CVERecord?id=CVE-2025-38455 Référence CVE CVE-2025-38456 https://www.cve.org/CVERecord?id=CVE-2025-38456 Référence CVE CVE-2025-38457 https://www.cve.org/CVERecord?id=CVE-2025-38457 Référence CVE CVE-2025-38458 https://www.cve.org/CVERecord?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2025-AVI-1075Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory

CERT-FR · French · CERTFR-2025-AVI-1073Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-38440 Référence CVE CVE-2025-38441 https://www.cve.org/CVERecord?id=CVE-2025-38441 Référence CVE CVE-2025-38443 https://www.cve.org/CVERecord?id=CVE-2025-38443 Référence CVE CVE-2025-38444 https://www.cve.org/CVERecord?id=CVE-2025-38444 Référence CVE CVE-2025-38445 https://www.cve.org/CVERecord?id=CVE-2025-38445 Référence CVE CVE-2025-38446 https://www.cve.org/CVERecord?id=CVE-2025-38446 Référence CVE CVE-2025-38448 https://www.cve.org/CVERecord?id=CVE-2025-38448 Référence CVE CVE-2025-38449 https://www.cve.org/CVERecord?id=CVE-2025-38449 Référence CVE CVE-2025-38450 https://www.cve.org/CVERecord?id=CVE-2025-38450 Référence CVE CVE-2025-38451 https://www.cve.org/CVERecord?id=CVE-2025-38451 Référence CVE CVE-2025-38453 https://www.cve.org/CVERecord?id=CVE-2025-38453 Référence CVE CVE-2025-38454 https://www.cve.org/CVERecord?id=CVE-2025-38454 Référence CVE CVE-2025-38455 https://www.cve.org/CVERecord?id=CVE-2025-38455 Référence CVE CVE-2025-38456 https://www.cve.org/CVERecord?id=CVE-2025-38456 Référence CVE CVE-2025-38457 https://www.cve.org/CVERecord?id=CVE-2025-38457 Référence CVE CVE-2025-38458 https://www.cve.org/CVERecord?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2025-AVI-1050Multiples vulnérabilités dans le noyau Linux d'Ubuntu

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0894Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2025-38428 Référence CVE CVE-2025-38430 https://www.cve.org/CVERecord?id=CVE-2025-38430 Référence CVE CVE-2025-38437 https://www.cve.org/CVERecord?id=CVE-2025-38437 Référence CVE CVE-2025-38439 https://www.cve.org/CVERecord?id=CVE-2025-38439 Référence CVE CVE-2025-38441 https://www.cve.org/CVERecord?id=CVE-2025-38441 Référence CVE CVE-2025-38443 https://www.cve.org/CVERecord?id=CVE-2025-38443 Référence CVE CVE-2025-38444 https://www.cve.org/CVERecord?id=CVE-2025-38444 Référence CVE CVE-2025-38445 https://www.cve.org/CVERecord?id=CVE-2025-38445 Référence CVE CVE-2025-38448 https://www.cve.org/CVERecord?id=CVE-2025-38448 Référence CVE CVE-2025-38451 https://www.cve.org/CVERecord?id=CVE-2025-38451 Référence CVE CVE-2025-38455 https://www.cve.org/CVERecord?id=CVE-2025-38455 Référence CVE CVE-2025-38456 https://www.cve.org/CVERecord?id=CVE-2025-38456 Référence CVE CVE-2025-38457 https://www.cve.org/CVERecord?id=CVE-2025-38457 Référence CVE CVE-2025-38458 https://www.cve.org/CVERecord?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=CVE-2025-38460 Référence CVE CVE-2025-38461 https://www.cve.org/CVERecord?id=CVE-2025-38461 Référence CVE CVE-2025-38462 https://www.cve.org/CVERecord?id=

Official advisory

CERT-FR · French · CERTFR-2025-AVI-0698Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2025-38440 Référence CVE CVE-2025-38441 https://www.cve.org/CVERecord?id=CVE-2025-38441 Référence CVE CVE-2025-38443 https://www.cve.org/CVERecord?id=CVE-2025-38443 Référence CVE CVE-2025-38444 https://www.cve.org/CVERecord?id=CVE-2025-38444 Référence CVE CVE-2025-38445 https://www.cve.org/CVERecord?id=CVE-2025-38445 Référence CVE CVE-2025-38446 https://www.cve.org/CVERecord?id=CVE-2025-38446 Référence CVE CVE-2025-38448 https://www.cve.org/CVERecord?id=CVE-2025-38448 Référence CVE CVE-2025-38449 https://www.cve.org/CVERecord?id=CVE-2025-38449 Référence CVE CVE-2025-38450 https://www.cve.org/CVERecord?id=CVE-2025-38450 Référence CVE CVE-2025-38451 https://www.cve.org/CVERecord?id=CVE-2025-38451 Référence CVE CVE-2025-38452 https://www.cve.org/CVERecord?id=CVE-2025-38452 Référence CVE CVE-2025-38454 https://www.cve.org/CVERecord?id=CVE-2025-38454 Référence CVE CVE-2025-38455 https://www.cve.org/CVERecord?id=CVE-2025-38455 Référence CVE CVE-2025-38456 https://www.cve.org/CVERecord?id=CVE-2025-38456 Référence CVE CVE-2025-38457 https://www.cve.org/CVERecord?id=CVE-2025-38457 Référence CVE CVE-2025-38458 https://www.cve.org/CVERecord?id=CVE-2025-38458 Référence CVE CVE-2025-38459 https://www.cve.org/CVERecord?id=CVE-2025-38459 Référence CVE CVE-2025-38460 https://www.cve.org/CVERecord?id=

Official advisory

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.5; SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5; SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5; SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5; SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Fixed: < 6.15; 6.1.146 ≤ 6.1.*; 6.6.99 ≤ 6.6.*; 6.12.39 ≤ 6.12.*; 6.15.7 ≤ 6.15.*; 6.16 ≤ *
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.

Evidence and provenance

Published 25 Jul 2025 · Last source change 14 Jul 2026, 12:42 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-08-14

European sourceENISA EUVD · EUVD-2025-22690

Product sourceVendor CSAF · Siemens ProductCERT

Remediation sourceVendor CSAF · Siemens ProductCERT

CWE sourceUnavailable

NVD statusNVD modified after enrichment

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates →

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

2025-07-25CVE published

2026-07-14Fixed release or patch reference recorded

ENISA EUVD · EUVD-2025-22690↗Vendor CSAF · Siemens ProductCERT↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

md/md-bitmap: fix GPF in bitmap_get_stats()

National CERT insights ?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

EUVD-2025-22690

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.