BlackTreeIndependent security intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-43071High confidence

dcache: Limit the minimal number of bucket to two

Linux · Linux

9.1CriticalCVSS 3.1
Recommended action
Within 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
Distribution package intelligence

Ubuntu vendor package status

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

20 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 releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, 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 feedCanonical record ↗Source updated 9 Sept 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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 feedCanonical 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-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
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.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: dcache: Limit the minimal number of bucket to two There is an OOB read problem on dentry_hashtable when user sets 'dhash_entries=1': BUG: unable to handle page fault for address: ffff888b30b774b0 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP PTI RIP: 0010:__d_lookup+0x56/0x120 Call Trace: d_lookup.cold+0x16/0x5d lookup_dcache+0x27/0xf0 lookup_one_qstr_excl+0x2a/0x180 start_dirop+0x55/0xa0 simple_start_creating+0x8d/0xa0 debugfs_start_creating+0x8c/0x180 debugfs_create_dir+0x1d/0x1c0 pinctrl_init+0x6d/0x140 do_one_initcall+0x6d/0x3d0 kernel_init_freeable+0x39f/0x460 kernel_init+0x2a/0x260 There will be only one bucket in dentry_hashtable when dhash_entries is set as one, and d_hash_shift is calculated as 32 by dcache_init(). Then, following process will access more than one buckets(which memory region is not allocated) in dentry_hashtable: d_lookup b = d_hash(hash) dentry_hashtable + ((u32)hashlen >> d_hash_shift) // The C standard defines the behavior of right shift amounts // exceeding the bit width of the operand as undefined. The // result of '(u32)hashlen >> d_hash_shift' becomes 'hashlen', // so 'b' will point to an unallocated memory region. hlist_bl_for_each_entry_rcu(b) hlist_bl_first_rcu(head) h->first // read OOB! Fix it by limiting the minimal number of dentry_hashtable bucket to two, so that 'd_hash_shift' won't exceeds the bit width of type u32.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
Optional official sources

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

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

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-2026-27375

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: dcache: Limit the minimal number of bucket to two There is an OOB read problem on dentry_hashtable when user sets 'dhash_entries=1': BUG: unable to handle page fault for address: ffff888b30b774b0 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP PTI RIP: 0010:__d_lookup+0x56/0x120 Call Trace: d_lookup.cold+0x16/0x5d lookup_dcache+0x27/0xf0 lookup_one_qstr_excl+0x2a/0x180 start_dirop+0x55/0xa0 simple_start_creating+0x8d/0xa0 debugfs_start_creating+0x8c/0x180 debugfs_create_dir+0x1d/0x1c0 pinctrl_init+0x6d/0x140 do_one_initcall+0x6d/0x3d0 kernel_init_freeable+0x39f/0x460 kernel_init+0x2a/0x260 There will be only one bucket in dentry_hashtable when dhash_entries is set as one, and d_hash_shift is calculated as 32 by dcache_init(). Then, following process will access more than one buckets(which memory region is not allocated) in dentry_hashtable: d_lookup b = d_hash(hash) dentry_hashtable + ((u32)hashlen >> d_hash_shift) // The C standard defines the behavior of right shift amounts // exceeding the bit width of the operand as undefined. The // result of '(u32)hashlen >> d_hash_shift' becomes 'hashlen', // so 'b' will point to an unallocated memory region. hlist_bl_for_each_entry_rcu(b) hlist_bl_first_rcu(head) h->first // read OOB! Fix it by limiting the minimal number of dentry_hashtable bucket to two, so that 'd_hash_shift' won't exceeds the bit width of type u32.

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
9.1 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 72 hours

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.

Patch available
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: dcache: Limit the minimal number of bucket to two There is an OOB read problem on dentry_hashtable when user sets 'dhash_entries=1': BUG: unable to handle page fault for address: ffff888b30b774b0 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP PTI RIP: 0010:__d_lookup+0x56/0x120 Call Trace: d_lookup.cold+0x16/0x5d lookup_dcache+0x27/0xf0 lookup_one_qstr_excl+0x2a/0x180 start_dirop+0x55/0xa0 simple_start_creating+0x8d/0xa0 debugfs_start_creating+0x8c/0x180 debugfs_create_dir+0x1d/0x1c0 pinctrl_init+0x6d/0x140 do_one_initcall+0x6d/0x3d0 kernel_init_freeable+0x39f/0x460 kernel_init+0x2a/0x260 There will be only one bucket in dentry_hashtable when dhash_entries is set as one, and d_hash_shift is calculated as 32 by dcache_init(). Then, following process will access more than one buckets(which memory region is not allocated) in dentry_hashtable: d_lookup b = d_hash(hash) dentry_hashtable + ((u32)hashlen >> d_hash_shift) // The C standard defines the behavior of right shift amounts // exceeding the bit width of the operand as undefined. The // result of '(u32)hashlen >> d_hash_shift' becomes 'hashlen', // so 'b' will point to an unallocated memory region. hlist_bl_for_each_entry_rcu(b) hlist_bl_first_rcu(head) h->first // read OOB! Fix it by limiting the minimal number of dentry_hashtable bucket to two, so that 'd_hash_shift' won't exceeds the bit width of type u32.

What

In the Linux kernel, the following vulnerability has been resolved: dcache: Limit the minimal number of bucket to two There is an OOB read problem on dentry_hashtable when user sets 'dhash_entries=1': BUG: unable to handle page fault for address: ffff888b30b774b0 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP PTI RIP: 0010:__d_lookup+0x56/0x120 Call Trace: d_lookup.cold+0x16/0x5d lookup_dcache+0x27/0xf0 lookup_one_qstr_excl+0x2a/0x180 start_dirop+0x55/0xa0 simple_start_creating+0x8d/0xa0 debugfs_start_creating+0x8c/0x180 debugfs_create_dir+0x1d/0x1c0 pinctrl_init+0x6d/0x140 do_one_initcall+0x6d/0x3d0 kernel_init_freeable+0x39f/0x460 kernel_init+0x2a/0x260 There will be only one bucket in dentry_hashtable when dhash_entries is set as one, and d_hash_shift is calculated as 32 by dcache_init(). Then, following process will access more than one buckets(which memory region is not allocated) in dentry_hashtable: d_lookup b = d_hash(hash) dentry_hashtable + ((u32)hashlen >> d_hash_shift) // The C standard defines the behavior of right shift amounts // exceeding the bit width of the operand as undefined. The // result of '(u32)hashlen >> d_hash_shift' becomes 'hashlen', // so 'b' will point to an unallocated memory region. hlist_bl_for_each_entry_rcu(b) hlist_bl_first_rcu(head) h->first // read OOB! Fix it by limiting the minimal number of dentry_hashtable bucket to two, so that 'd_hash_shift' won't exceeds the bit width of type u32.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In the Linux kernel, the following vulnerability has been resolved: dcache: Limit the minimal number of bucket to two There is an OOB read problem on dentry_hashtable when user sets 'dhash_entries=1': BUG: unable to handle page fault for address: ffff888b30b774b0 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP PTI RIP: 0010:__d_lookup+0x56/0x120 Call Trace: d_lookup.cold+0x16/0x5d lookup_dcache+0x27/0xf0 lookup_one_qstr_excl+0x2a/0x180 start_dirop+0x55/0xa0 simple_start_creating+0x8d/0xa0 debugfs_start_creating+0x8c/0x180 debugfs_create_dir+0x1d/0x1c0 pinctrl_init+0x6d/0x140 do_one_initcall+0x6d/0x3d0 kernel_init_freeable+0x39f/0x460 kernel_init+0x2a/0x260 There will be only one bucket in dentry_hashtable when dhash_entries is set as one, and d_hash_shift is calculated as 32 by dcache_init(). Then, following process will access more than one buckets(which memory region is not allocated) in dentry_hashtable: d_lookup b = d_hash(hash) dentry_hashtable + ((u32)hashlen >> d_hash_shift) // The C standard defines the behavior of right shift amounts // exceeding the bit width of the operand as undefined. The // result of '(u32)hashlen >> d_hash_shift' becomes 'hashlen', // so 'b' will point to an unallocated memory region. hlist_bl_for_each_entry_rcu(b) hlist_bl_first_rcu(head) h->first // read OOB! Fix it by limiting the minimal number of dentry_hashtable bucket to two, so that 'd_hash_shift' won't exceeds the bit width of type u32.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

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
a network path → Out-of-bounds Read → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
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: a standard category for the underlying weakness.
CWE-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.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
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-125
A

Official authority intelligence

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

ENISA EUVD · EUVD-2026-27375Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: dcache: Limit the minimal number of bucket to two There is an OOB read problem on dentry_hashtable when user sets 'dhash_entries=1': BUG: unable to handle page fault for address: ffff888b30b774b0 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page Oops: Oops: 0000 [#1] SMP PTI RIP: 0010:__d_lookup+0x56/0x120 Call Trace: d_lookup.cold+0x16/0x5d lookup_dcache+0x27/0xf0 lookup_one_qstr_excl+0x2a/0x180 start_dirop+0x55/0xa0 simple_start_creating+0x8d/0xa0 debugfs_start_creating+0x8c/0x180 debugfs_create_dir+0x1d/0x1c0 pinctrl_init+0x6d/0x140 do_one_initcall+0x6d/0x3d0 kernel_init_freeable+0x39f/0x460 kernel_init+0x2a/0x260 There will be only one bucket in dentry_hashtable when dhash_entries is set as one, and d_hash_shift is calculated as 32 by dcache_init(). Then, following process will access more than one buckets(which memory region is not allocated) in dentry_hashtable: d_lookup b = d_hash(hash) dentry_hashtable + ((u32)hashlen >> d_hash_shift) // The C standard defines the behavior of right shift amounts // exceeding the bit width of the operand as undefined. The // result of '(u32)hashlen >> d_hash_shift' becomes 'hashlen', // so 'b' will point to an unallocated memory region. hlist_bl_for_each_entry_rcu(b) hlist_bl_first_rcu(head) h->first // read OOB! Fix it by limiting the minimal number of dentry_hashtable bucket to two, so that 'd_hash_shift' won't exceeds the bit width of type u32.

Official EUVD record
BSI · German · WID-SEC-W-2026-1385Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service zu verursachen, Informationen offenzulegen, Sicherheitsmaßnahmen zu umgehen oder potentiell beliebigen Programmcode auszuführen.

Official advisory
CERT-FR · French · CERTFR-2026-AVI-1117Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2021-47378 Référence CVE CVE-2025-27558 https://www.cve.org/CVERecord?id=CVE-2025-27558 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-31405 https://www.cve.org/CVERecord?id=CVE-2026-31405 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31657 https://www.cve.org/CVERecord?id=CVE-2026-31657 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31705 https://www.cve.org/CVERecord?id=CVE-2026-31705 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43378 https://www.cve.org/CVERecord?id=CVE-2026-43378 Référence CVE CVE-2026-43493 https://www.cve.org/CVERecord?id=CVE-2026-43493 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-46266 https://www.cve.org/CVERecord?id=CVE-2026-46266 Référence CVE CVE-2026-46331 https://www.cve.org/CVERecord?id=CVE-2026-46331 Référence CVE CVE-2026-52914 https://www.cve.org/CVERecord?id=CVE-2026-52914 Référence CVE CVE-2026-52924 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-1093Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43054 Référence CVE CVE-2026-43058 https://www.cve.org/CVERecord?id=CVE-2026-43058 Référence CVE CVE-2026-43060 https://www.cve.org/CVERecord?id=CVE-2026-43060 Référence CVE CVE-2026-43061 https://www.cve.org/CVERecord?id=CVE-2026-43061 Référence CVE CVE-2026-43062 https://www.cve.org/CVERecord?id=CVE-2026-43062 Référence CVE CVE-2026-43065 https://www.cve.org/CVERecord?id=CVE-2026-43065 Référence CVE CVE-2026-43066 https://www.cve.org/CVERecord?id=CVE-2026-43066 Référence CVE CVE-2026-43068 https://www.cve.org/CVERecord?id=CVE-2026-43068 Référence CVE CVE-2026-43069 https://www.cve.org/CVERecord?id=CVE-2026-43069 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43059 Référence CVE CVE-2026-43060 https://www.cve.org/CVERecord?id=CVE-2026-43060 Référence CVE CVE-2026-43061 https://www.cve.org/CVERecord?id=CVE-2026-43061 Référence CVE CVE-2026-43062 https://www.cve.org/CVERecord?id=CVE-2026-43062 Référence CVE CVE-2026-43064 https://www.cve.org/CVERecord?id=CVE-2026-43064 Référence CVE CVE-2026-43065 https://www.cve.org/CVERecord?id=CVE-2026-43065 Référence CVE CVE-2026-43066 https://www.cve.org/CVERecord?id=CVE-2026-43066 Référence CVE CVE-2026-43068 https://www.cve.org/CVERecord?id=CVE-2026-43068 Référence CVE CVE-2026-43069 https://www.cve.org/CVERecord?id=CVE-2026-43069 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43072 https://www.cve.org/CVERecord?id=CVE-2026-43072 Référence CVE CVE-2026-43073 https://www.cve.org/CVERecord?id=CVE-2026-43073 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43081 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43059 Référence CVE CVE-2026-43060 https://www.cve.org/CVERecord?id=CVE-2026-43060 Référence CVE CVE-2026-43061 https://www.cve.org/CVERecord?id=CVE-2026-43061 Référence CVE CVE-2026-43062 https://www.cve.org/CVERecord?id=CVE-2026-43062 Référence CVE CVE-2026-43064 https://www.cve.org/CVERecord?id=CVE-2026-43064 Référence CVE CVE-2026-43065 https://www.cve.org/CVERecord?id=CVE-2026-43065 Référence CVE CVE-2026-43066 https://www.cve.org/CVERecord?id=CVE-2026-43066 Référence CVE CVE-2026-43068 https://www.cve.org/CVERecord?id=CVE-2026-43068 Référence CVE CVE-2026-43069 https://www.cve.org/CVERecord?id=CVE-2026-43069 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43072 https://www.cve.org/CVERecord?id=CVE-2026-43072 Référence CVE CVE-2026-43073 https://www.cve.org/CVERecord?id=CVE-2026-43073 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43081 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-43059 Référence CVE CVE-2026-43060 https://www.cve.org/CVERecord?id=CVE-2026-43060 Référence CVE CVE-2026-43061 https://www.cve.org/CVERecord?id=CVE-2026-43061 Référence CVE CVE-2026-43062 https://www.cve.org/CVERecord?id=CVE-2026-43062 Référence CVE CVE-2026-43064 https://www.cve.org/CVERecord?id=CVE-2026-43064 Référence CVE CVE-2026-43065 https://www.cve.org/CVERecord?id=CVE-2026-43065 Référence CVE CVE-2026-43066 https://www.cve.org/CVERecord?id=CVE-2026-43066 Référence CVE CVE-2026-43068 https://www.cve.org/CVERecord?id=CVE-2026-43068 Référence CVE CVE-2026-43069 https://www.cve.org/CVERecord?id=CVE-2026-43069 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43072 https://www.cve.org/CVERecord?id=CVE-2026-43072 Référence CVE CVE-2026-43073 https://www.cve.org/CVERecord?id=CVE-2026-43073 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43081 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0898Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31659 Référence CVE CVE-2026-31668 https://www.cve.org/CVERecord?id=CVE-2026-31668 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31682 https://www.cve.org/CVERecord?id=CVE-2026-31682 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31718 https://www.cve.org/CVERecord?id=CVE-2026-31718 Référence CVE CVE-2026-43011 https://www.cve.org/CVERecord?id=CVE-2026-43011 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=CVE-2026-43114 Référence CVE CVE-2026-43117 https://www.cve.org/CVERecord?id=CVE-2026-43117 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43185 https://www.cve.org/CVERecord?id=CVE-2026-43185 Référence CVE CVE-2026-43186 https://www.cve.org/CVERecord?id=CVE-2026-43186 Référence CVE CVE-2026-43197 https://www.cve.org/CVERecord?id=CVE-2026-43197 Référence CVE CVE-2026-43304 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0862Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-31711 Référence CVE CVE-2026-31712 https://www.cve.org/CVERecord?id=CVE-2026-31712 Référence CVE CVE-2026-31715 https://www.cve.org/CVERecord?id=CVE-2026-31715 Référence CVE CVE-2026-31716 https://www.cve.org/CVERecord?id=CVE-2026-31716 Référence CVE CVE-2026-31732 https://www.cve.org/CVERecord?id=CVE-2026-31732 Référence CVE CVE-2026-43010 https://www.cve.org/CVERecord?id=CVE-2026-43010 Référence CVE CVE-2026-43052 https://www.cve.org/CVERecord?id=CVE-2026-43052 Référence CVE CVE-2026-43058 https://www.cve.org/CVERecord?id=CVE-2026-43058 Référence CVE CVE-2026-43064 https://www.cve.org/CVERecord?id=CVE-2026-43064 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43072 https://www.cve.org/CVERecord?id=CVE-2026-43072 Référence CVE CVE-2026-43075 https://www.cve.org/CVERecord?id=CVE-2026-43075 Référence CVE CVE-2026-43076 https://www.cve.org/CVERecord?id=CVE-2026-43076 Référence CVE CVE-2026-43079 https://www.cve.org/CVERecord?id=CVE-2026-43079 Référence CVE CVE-2026-43080 https://www.cve.org/CVERecord?id=CVE-2026-43080 Référence CVE CVE-2026-43085 https://www.cve.org/CVERecord?id=CVE-2026-43085 Référence CVE CVE-2026-43089 https://www.cve.org/CVERecord?id=CVE-2026-43089 Référence CVE CVE-2026-43093 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0861Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31716 Référence CVE CVE-2026-31717 https://www.cve.org/CVERecord?id=CVE-2026-31717 Référence CVE CVE-2026-31718 https://www.cve.org/CVERecord?id=CVE-2026-31718 Référence CVE CVE-2026-31719 https://www.cve.org/CVERecord?id=CVE-2026-31719 Référence CVE CVE-2026-43011 https://www.cve.org/CVERecord?id=CVE-2026-43011 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43058 https://www.cve.org/CVERecord?id=CVE-2026-43058 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43072 https://www.cve.org/CVERecord?id=CVE-2026-43072 Référence CVE CVE-2026-43073 https://www.cve.org/CVERecord?id=CVE-2026-43073 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=CVE-2026-43114 Référence CVE CVE-2026-43117 https://www.cve.org/CVERecord?id=CVE-2026-43117 Référence CVE CVE-2026-43123 https://www.cve.org/CVERecord?id=

Official advisory
CERT-FR · French · CERTFR-2026-AVI-0831Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31716 Référence CVE CVE-2026-31717 https://www.cve.org/CVERecord?id=CVE-2026-31717 Référence CVE CVE-2026-31718 https://www.cve.org/CVERecord?id=CVE-2026-31718 Référence CVE CVE-2026-31719 https://www.cve.org/CVERecord?id=CVE-2026-31719 Référence CVE CVE-2026-43011 https://www.cve.org/CVERecord?id=CVE-2026-43011 Référence CVE CVE-2026-43033 https://www.cve.org/CVERecord?id=CVE-2026-43033 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43058 https://www.cve.org/CVERecord?id=CVE-2026-43058 Référence CVE CVE-2026-43071 https://www.cve.org/CVERecord?id=CVE-2026-43071 Référence CVE CVE-2026-43072 https://www.cve.org/CVERecord?id=CVE-2026-43072 Référence CVE CVE-2026-43073 https://www.cve.org/CVERecord?id=CVE-2026-43073 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43078 https://www.cve.org/CVERecord?id=CVE-2026-43078 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43114 https://www.cve.org/CVERecord?id=CVE-2026-43114 Référence CVE CVE-2026-43117 https://www.cve.org/CVERecord?id=CVE-2026-43117 Référence CVE CVE-2026-43123 https://www.cve.org/CVERecord?id=

Official advisory
03

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.6; SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6; SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6; SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6; SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Fixed
< 3.17; 6.1.175 ≤ 6.1.*; 6.6.136 ≤ 6.6.*; 6.12.83 ≤ 6.12.*; 6.18.24 ≤ 6.18.*; 6.19.14 ≤ 6.19.*; 7.0.1 ≤ 7.0.*; 7.1 ≤ *
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.
04

Evidence and provenance

Published 5 May 2026 · Last source change 8 Sept 2026, 08:48 UTC · CWE-125 · Out-of-bounds Read

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-2026-27375
Product sourceVendor CSAF · Siemens ProductCERT
Remediation sourceVendor CSAF · Siemens ProductCERT
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

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.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-27375↗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.
Free version - for non-commercial use only.CVE-2026-43071 · cve.blacktree.nl