BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-43158High confidence

xfs: fix freemap adjustments when adding xattrs to leaf blocks

Linux · Linux

8.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.68% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.6-1Debian Security Tracker ↗Source updated 6 Oct 2026
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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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 Ubuntu Security ↗Source updated 5 Oct 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
CVE-2026-43158 · CSAF 2.0 · revision 23 · interimSUSE Product Security TeamCVE-2026-43158
262 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: xfs: fix freemap adjustments when adding xattrs to leaf blocks xfs/592 and xfs/794 both trip this assertion in the leaf block freemap adjustment code after ~20 minutes of running on my test VMs: ASSERT(ichdr->firstused >= ichdr->count * sizeof(xfs_attr_leaf_entry_t) + xfs_attr3_leaf_hdr_size(leaf)); Upon enabling quite a lot more debugging code, I narrowed this down to fsstress trying to set a local extended attribute with namelen=3 and valuelen=71. This results in an entry size of 80 bytes. At the start of xfs_attr3_leaf_add_work, the freemap looks like this: i 0 base 448 size 0 rhs 448 count 46 i 1 base 388 size 132 rhs 448 count 46 i 2 base 2120 size 4 rhs 448 count 46 firstused = 520 where "rhs" is the first byte past the end of the leaf entry array. This is inconsistent -- the entries array ends at byte 448, but freemap[1] says there's free space starting at byte 388! By the end of the function, the freemap is in worse shape: i 0 base 456 size 0 rhs 456 count 47 i 1 base 388 size 52 rhs 456 count 47 i 2 base 2120 size 4 rhs 456 count 47 firstused = 440 Important note: 388 is not aligned with the entries array element size of 8 bytes. Based on the incorrect freemap, the name area starts at byte 440, which is below the end of the entries array! That's why the assertion triggers and the filesystem shuts down. How did we end up here? First, recall from the previous patch that the freemap array in an xattr leaf block is not intended to be a comprehensive map of all free space in the leaf block. In other words, it's perfectly legal to have a leaf block with: * 376 bytes in use by the entries array * freemap[0] has [base = 376, size = 8] * freemap[1] has [base = 388, size = 1500] * the space between 376 and 388 is free, but the freemap stopped tracking that some time ago If we add one xattr, the entries array grows to 384 bytes, and freemap[0] becomes [base = 384, size = 0]. So far, so good. But if we add a second xattr, the entries array grows to 392 bytes, and freemap[0] gets pushed up to [base = 392, size = 0]. This is bad, because freemap[1] hasn't been updated, and now the entries array and the free space claim the same space. The fix here is to adjust all freemap entries so that none of them collide with the entries array. Note that this fix relies on commit 2a2b5932db6758 ("xfs: fix attr leaf header freemap.size underflow") and the previous patch that resets zero length freemap entries to have base = 0.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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

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 actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 20 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: xfs: fix freemap adjustments when adding xattrs to leaf blocks xfs/592 and xfs/794 both trip this assertion in the leaf block freemap adjustment code after ~20 minutes of running on my test VMs: ASSERT(ichdr->firstused >= ichdr->count * sizeof(xfs_attr_leaf_entry_t) + xfs_attr3_leaf_hdr_size(leaf)); Upon enabling quite a lot more debugging code, I narrowed this down to fsstress trying to set a local extended attribute with namelen=3 and valuelen=71. This results in an entry size of 80 bytes. At the start of xfs_attr3_leaf_add_work, the freemap looks like this: i 0 base 448 size 0 rhs 448 count 46 i 1 base 388 size 132 rhs 448 count 46 i 2 base 2120 size 4 rhs 448 count 46 firstused = 520 where "rhs" is the first byte past the end of the leaf entry array. This is inconsistent -- the entries array ends at byte 448, but freemap[1] says there's free space starting at byte 388! By the end of the function, the freemap is in worse shape: i 0 base 456 size 0 rhs 456 count 47 i 1 base 388 size 52 rhs 456 count 47 i 2 base 2120 size 4 rhs 456 count 47 firstused = 440 Important note: 388 is not aligned with the entries array element size of 8 bytes. Based on the incorrect freemap, the name area starts at byte 440, which is below the end of the entries array! That's why the assertion triggers and the filesystem shuts down. How did we end up here? First, recall from the previous patch that the freemap array in an xattr leaf block is not intended to be a comprehensive map of all free space in the leaf block. In other words, it's perfectly legal to have a leaf block with: * 376 bytes in use by the entries array * freemap[0] has [base = 376, size = 8] * freemap[1] has [base = 388, size = 1500] * the space between 376 and 388 is free, but the freemap stopped tracking that some time ago If we add one xattr, the entries array grows to 384 bytes, and freemap[0] becomes [base = 384, size = 0]. So far, so good. But if we add a second xattr, the entries array grows to 392 bytes, and freemap[0] gets pushed up to [base = 392, size = 0]. This is bad, because freemap[1] hasn't been updated, and now the entries array and the free space claim the same space. The fix here is to adjust all freemap entries so that none of them collide with the entries array. Note that this fix relies on commit 2a2b5932db6758 ("xfs: fix attr leaf header freemap.size underflow") and the previous patch that resets zero length freemap entries to have base = 0.

What

In the Linux kernel, the following vulnerability has been resolved: xfs: fix freemap adjustments when adding xattrs to leaf blocks xfs/592 and xfs/794 both trip this assertion in the leaf block freemap adjustment code after ~20 minutes of running on my test VMs: ASSERT(ichdr->firstused >= ichdr->count * sizeof(xfs_attr_leaf_entry_t) + xfs_attr3_leaf_hdr_size(leaf)); Upon enabling quite a lot more debugging code, I narrowed this down to fsstress trying to set a local extended attribute with namelen=3 and valuelen=71. This results in an entry size of 80 bytes. At the start of xfs_attr3_leaf_add_work, the freemap looks like this: i 0 base 448 size 0 rhs 448 count 46 i 1 base 388 size 132 rhs 448 count 46 i 2 base 2120 size 4 rhs 448 count 46 firstused = 520 where "rhs" is the first byte past the end of the leaf entry array. This is inconsistent -- the entries array ends at byte 448, but freemap[1] says there's free space starting at byte 388! By the end of the function, the freemap is in worse shape: i 0 base 456 size 0 rhs 456 count 47 i 1 base 388 size 52 rhs 456 count 47 i 2 base 2120 size 4 rhs 456 count 47 firstused = 440 Important note: 388 is not aligned with the entries array element size of 8 bytes. Based on the incorrect freemap, the name area starts at byte 440, which is below the end of the entries array! That's why the assertion triggers and the filesystem shuts down. How did we end up here? First, recall from the previous patch that the freemap array in an xattr leaf block is not intended to be a comprehensive map of all free space in the leaf block. In other words, it's perfectly legal to have a leaf block with: * 376 bytes in use by the entries array * freemap[0] has [base = 376, size = 8] * freemap[1] has [base = 388, size = 1500] * the space between 376 and 388 is free, but the freemap stopped tracking that some time ago If we add one xattr, the entries array grows to 384 bytes, and freemap[0] becomes [base = 384, size = 0]. So far, so good. But if we add a second xattr, the entries array grows to 392 bytes, and freemap[0] gets pushed up to [base = 392, size = 0]. This is bad, because freemap[1] hasn't been updated, and now the entries array and the free space claim the same space. The fix here is to adjust all freemap entries so that none of them collide with the entries array. Note that this fix relies on commit 2a2b5932db6758 ("xfs: fix attr leaf header freemap.size underflow") and the previous patch that resets zero length freemap entries to have base = 0.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through a network path may attempt exploitation with low privileges. 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: xfs: fix freemap adjustments when adding xattrs to leaf blocks xfs/592 and xfs/794 both trip this assertion in the leaf block freemap adjustment code after ~20 minutes of running on my test VMs: ASSERT(ichdr->firstused >= ichdr->count * sizeof(xfs_attr_leaf_entry_t) + xfs_attr3_leaf_hdr_size(leaf)); Upon enabling quite a lot more debugging code, I narrowed this down to fsstress trying to set a local extended attribute with namelen=3 and valuelen=71. This results in an entry size of 80 bytes. At the start of xfs_attr3_leaf_add_work, the freemap looks like this: i 0 base 448 size 0 rhs 448 count 46 i 1 base 388 size 132 rhs 448 count 46 i 2 base 2120 size 4 rhs 448 count 46 firstused = 520 where "rhs" is the first byte past the end of the leaf entry array. This is inconsistent -- the entries array ends at byte 448, but freemap[1] says there's free space starting at byte 388! By the end of the function, the freemap is in worse shape: i 0 base 456 size 0 rhs 456 count 47 i 1 base 388 size 52 rhs 456 count 47 i 2 base 2120 size 4 rhs 456 count 47 firstused = 440 Important note: 388 is not aligned with the entries array element size of 8 bytes. Based on the incorrect freemap, the name area starts at byte 440, which is below the end of the entries array! That's why the assertion triggers and the filesystem shuts down. How did we end up here? First, recall from the previous patch that the freemap array in an xattr leaf block is not intended to be a comprehensive map of all free space in the leaf block. In other words, it's perfectly legal to have a leaf block with: * 376 bytes in use by the entries array * freemap[0] has [base = 376, size = 8] * freemap[1] has [base = 388, size = 1500] * the space between 376 and 388 is free, but the freemap stopped tracking that some time ago If we add one xattr, the entries array grows to 384 bytes, and freemap[0] becomes [base = 384, size = 0]. So far, so good. But if we add a second xattr, the entries array grows to 392 bytes, and freemap[0] gets pushed up to [base = 392, size = 0]. This is bad, because freemap[1] hasn't been updated, and now the entries array and the free space claim the same space. The fix here is to adjust all freemap entries so that none of them collide with the entries array. Note that this fix relies on commit 2a2b5932db6758 ("xfs: fix attr leaf header freemap.size underflow") and the previous patch that resets zero length freemap entries to have base = 0.

Why

A bounds error lets data be written beyond the intended memory region, potentially corrupting control data.

How

An attacker operating through a network path may attempt exploitation with low privileges. 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 Write → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
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: a standard category for the underlying weakness.
CWE-787 ↗

CWE-787: Out-of-bounds Write. The product writes 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:L/UI:N/S:U/C:H/I:H/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.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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.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.
NetworkCWE-787
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-1405Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um nicht spezifizierte Angriffe durchzuführen, möglicherweise Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren oder offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.

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

d?id=CVE-2026-43139 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43145 https://www.cve.org/CVERecord?id=CVE-2026-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43148 https://www.cve.org/CVERecord?id=CVE-2026-43148 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=CVE-2026-43168 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=CVE-2026-43171 Référence CVE CVE-2026-43180 https://www.cve.org/CVERecord?id=CVE-2026-43180 Référence CVE CVE-2026-43182 https://www.cve.org/CVERecord?id=CVE-2026-43182 Référence CVE CVE-2026-43183 https://www.cve.org/CVERecord?id=CVE-2026-43183 Référence CVE CVE-2026-43184 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-43139 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43145 https://www.cve.org/CVERecord?id=CVE-2026-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43148 https://www.cve.org/CVERecord?id=CVE-2026-43148 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=CVE-2026-43168 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=CVE-2026-43171 Référence CVE CVE-2026-43180 https://www.cve.org/CVERecord?id=CVE-2026-43180 Référence CVE CVE-2026-43182 https://www.cve.org/CVERecord?id=CVE-2026-43182 Référence CVE CVE-2026-43183 https://www.cve.org/CVERecord?id=CVE-2026-43183 Référence CVE CVE-2026-43184 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0986Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-42944 Référence CVE CVE-2026-42959 https://www.cve.org/CVERecord?id=CVE-2026-42959 Référence CVE CVE-2026-43020 https://www.cve.org/CVERecord?id=CVE-2026-43020 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 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-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43329 https://www.cve.org/CVERecord?id=CVE-2026-43329 Référence CVE CVE-2026-43512 https://www.cve.org/CVERecord?id=CVE-2026-43512 Référence CVE CVE-2026-43513 https://www.cve.org/CVERecord?id=CVE-2026-43513 Référence CVE CVE-2026-43514 https://www.cve.org/CVERecord?id=CVE-2026-43514 Référence CVE CVE-2026-43515 https://www.cve.org/CVERecord?id=CVE-2026-43515 Référence CVE CVE-2026-43618 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43139 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43145 https://www.cve.org/CVERecord?id=CVE-2026-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43148 https://www.cve.org/CVERecord?id=CVE-2026-43148 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=CVE-2026-43168 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=CVE-2026-43171 Référence CVE CVE-2026-43180 https://www.cve.org/CVERecord?id=CVE-2026-43180 Référence CVE CVE-2026-43182 https://www.cve.org/CVERecord?id=CVE-2026-43182 Référence CVE CVE-2026-43183 https://www.cve.org/CVERecord?id=CVE-2026-43183 Référence CVE CVE-2026-43184 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0956Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43119 Référence CVE CVE-2026-43120 https://www.cve.org/CVERecord?id=CVE-2026-43120 Référence CVE CVE-2026-43124 https://www.cve.org/CVERecord?id=CVE-2026-43124 Référence CVE CVE-2026-43128 https://www.cve.org/CVERecord?id=CVE-2026-43128 Référence CVE CVE-2026-43130 https://www.cve.org/CVERecord?id=CVE-2026-43130 Référence CVE CVE-2026-43132 https://www.cve.org/CVERecord?id=CVE-2026-43132 Référence CVE CVE-2026-43139 https://www.cve.org/CVERecord?id=CVE-2026-43139 Référence CVE CVE-2026-43145 https://www.cve.org/CVERecord?id=CVE-2026-43145 Référence CVE CVE-2026-43157 https://www.cve.org/CVERecord?id=CVE-2026-43157 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43161 https://www.cve.org/CVERecord?id=CVE-2026-43161 Référence CVE CVE-2026-43167 https://www.cve.org/CVERecord?id=CVE-2026-43167 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=CVE-2026-43171 Référence CVE CVE-2026-43175 https://www.cve.org/CVERecord?id=CVE-2026-43175 Référence CVE CVE-2026-43187 https://www.cve.org/CVERecord?id=CVE-2026-43187 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43191 https://www.cve.org/CVERecord?id=CVE-2026-43191 Référence CVE CVE-2026-43194 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-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43148 https://www.cve.org/CVERecord?id=CVE-2026-43148 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43150 https://www.cve.org/CVERecord?id=CVE-2026-43150 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43153 https://www.cve.org/CVERecord?id=CVE-2026-43153 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43157 https://www.cve.org/CVERecord?id=CVE-2026-43157 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43162 https://www.cve.org/CVERecord?id=CVE-2026-43162 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43167 https://www.cve.org/CVERecord?id=CVE-2026-43167 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=CVE-2026-43168 Référence CVE CVE-2026-43169 https://www.cve.org/CVERecord?id=CVE-2026-43169 Référence CVE CVE-2026-43170 https://www.cve.org/CVERecord?id=CVE-2026-43170 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0928Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-31530 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31607 https://www.cve.org/CVERecord?id=CVE-2026-31607 Référence CVE CVE-2026-31613 https://www.cve.org/CVERecord?id=CVE-2026-31613 Référence CVE CVE-2026-31684 https://www.cve.org/CVERecord?id=CVE-2026-31684 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=CVE-2026-43279 Référence CVE CVE-2026-43499 https://www.cve.org/CVERecord?id=CVE-2026-43499 Référence CVE CVE-2026-45852 https://www.cve.org/CVERecord?id=CVE-2026-45852 Référence CVE CVE-2026-46090 https://www.cve.org/CVERecord?id=CVE-2026-46090 Référence CVE CVE-2026-46099 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0927Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43143 https://www.cve.org/CVERecord?id=CVE-2026-43143 Référence CVE CVE-2026-43145 https://www.cve.org/CVERecord?id=CVE-2026-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43157 https://www.cve.org/CVERecord?id=CVE-2026-43157 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43161 https://www.cve.org/CVERecord?id=CVE-2026-43161 Référence CVE CVE-2026-43162 https://www.cve.org/CVERecord?id=CVE-2026-43162 Référence CVE CVE-2026-43167 https://www.cve.org/CVERecord?id=CVE-2026-43167 Référence CVE CVE-2026-43169 https://www.cve.org/CVERecord?id=CVE-2026-43169 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=CVE-2026-43171 Référence CVE CVE-2026-43175 https://www.cve.org/CVERecord?id=CVE-2026-43175 Référence CVE CVE-2026-43177 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-43139 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43145 https://www.cve.org/CVERecord?id=CVE-2026-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43148 https://www.cve.org/CVERecord?id=CVE-2026-43148 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43162 https://www.cve.org/CVERecord?id=CVE-2026-43162 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=CVE-2026-43168 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=CVE-2026-43171 Référence CVE CVE-2026-43180 https://www.cve.org/CVERecord?id=CVE-2026-43180 Référence CVE CVE-2026-43182 https://www.cve.org/CVERecord?id=CVE-2026-43182 Référence CVE CVE-2026-43183 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0864Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43093 Référence CVE CVE-2026-43094 https://www.cve.org/CVERecord?id=CVE-2026-43094 Référence CVE CVE-2026-43101 https://www.cve.org/CVERecord?id=CVE-2026-43101 Référence CVE CVE-2026-43107 https://www.cve.org/CVERecord?id=CVE-2026-43107 Référence CVE CVE-2026-43109 https://www.cve.org/CVERecord?id=CVE-2026-43109 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43119 https://www.cve.org/CVERecord?id=CVE-2026-43119 Référence CVE CVE-2026-43128 https://www.cve.org/CVERecord?id=CVE-2026-43128 Référence CVE CVE-2026-43139 https://www.cve.org/CVERecord?id=CVE-2026-43139 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=CVE-2026-43171 Référence CVE CVE-2026-43187 https://www.cve.org/CVERecord?id=CVE-2026-43187 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-43233 https://www.cve.org/CVERecord?id=CVE-2026-43233 Référence CVE CVE-2026-43234 https://www.cve.org/CVERecord?id=CVE-2026-43234 Référence CVE CVE-2026-43238 https://www.cve.org/CVERecord?id=CVE-2026-43238 Référence CVE CVE-2026-43239 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-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43148 https://www.cve.org/CVERecord?id=CVE-2026-43148 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43150 https://www.cve.org/CVERecord?id=CVE-2026-43150 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43153 https://www.cve.org/CVERecord?id=CVE-2026-43153 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43157 https://www.cve.org/CVERecord?id=CVE-2026-43157 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43167 https://www.cve.org/CVERecord?id=CVE-2026-43167 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=CVE-2026-43168 Référence CVE CVE-2026-43169 https://www.cve.org/CVERecord?id=CVE-2026-43169 Référence CVE CVE-2026-43170 https://www.cve.org/CVERecord?id=CVE-2026-43170 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=CVE-2026-43171 Référence CVE CVE-2026-43173 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0833Multiples vulnérabilités dans le noyau Linux de SUSE

d?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-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43083 https://www.cve.org/CVERecord?id=CVE-2026-43083 Référence CVE CVE-2026-43101 https://www.cve.org/CVERecord?id=CVE-2026-43101 Référence CVE CVE-2026-43109 https://www.cve.org/CVERecord?id=CVE-2026-43109 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43119 https://www.cve.org/CVERecord?id=CVE-2026-43119 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=CVE-2026-43171 Référence CVE CVE-2026-43187 https://www.cve.org/CVERecord?id=CVE-2026-43187 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-43234 https://www.cve.org/CVERecord?id=CVE-2026-43234 Référence CVE CVE-2026-43239 https://www.cve.org/CVERecord?id=CVE-2026-43239 Référence CVE CVE-2026-43249 https://www.cve.org/CVERecord?id=CVE-2026-43249 Référence CVE CVE-2026-43252 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-43145 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43148 https://www.cve.org/CVERecord?id=CVE-2026-43148 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43150 https://www.cve.org/CVERecord?id=CVE-2026-43150 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43153 https://www.cve.org/CVERecord?id=CVE-2026-43153 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43157 https://www.cve.org/CVERecord?id=CVE-2026-43157 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43167 https://www.cve.org/CVERecord?id=CVE-2026-43167 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=CVE-2026-43168 Référence CVE CVE-2026-43169 https://www.cve.org/CVERecord?id=CVE-2026-43169 Référence CVE CVE-2026-43170 https://www.cve.org/CVERecord?id=CVE-2026-43170 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=CVE-2026-43171 Référence CVE CVE-2026-43173 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0782Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-43063 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-43077 https://www.cve.org/CVERecord?id=CVE-2026-43077 Référence CVE CVE-2026-43109 https://www.cve.org/CVERecord?id=CVE-2026-43109 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43150 https://www.cve.org/CVERecord?id=CVE-2026-43150 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43184 https://www.cve.org/CVERecord?id=CVE-2026-43184 Référence CVE CVE-2026-43187 https://www.cve.org/CVERecord?id=CVE-2026-43187 Référence CVE CVE-2026-43197 https://www.cve.org/CVERecord?id=CVE-2026-43197 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43206 https://www.cve.org/CVERecord?id=CVE-2026-43206 Référence CVE CVE-2026-43234 https://www.cve.org/CVERecord?id=CVE-2026-43234 Référence CVE CVE-2026-43249 https://www.cve.org/CVERecord?id=CVE-2026-43249 Référence CVE CVE-2026-43252 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0781Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-35385 Référence CVE CVE-2026-39979 https://www.cve.org/CVERecord?id=CVE-2026-39979 Référence CVE CVE-2026-40164 https://www.cve.org/CVERecord?id=CVE-2026-40164 Référence CVE CVE-2026-41035 https://www.cve.org/CVERecord?id=CVE-2026-41035 Référence CVE CVE-2026-41326 https://www.cve.org/CVERecord?id=CVE-2026-41326 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-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Référence CVE CVE-2026-43303 https://www.cve.org/CVERecord?id=CVE-2026-43303 Référence CVE CVE-2026-43329 https://www.cve.org/CVERecord?id=CVE-2026-43329 Référence CVE CVE-2026-46056 https://www.cve.org/CVERecord?id=CVE-2026-46056 Référence CVE CVE-2026-46125 https://www.cve.org/CVERecord?id=CVE-2026-46125 Référence CVE CVE-2026-46152 https://www.cve.org/CVERecord?id=CVE-2026-46152 Référence CVE CVE-2026-46227 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2026-43135 Référence CVE CVE-2026-43136 https://www.cve.org/CVERecord?id=CVE-2026-43136 Référence CVE CVE-2026-43139 https://www.cve.org/CVERecord?id=CVE-2026-43139 Référence CVE CVE-2026-43140 https://www.cve.org/CVERecord?id=CVE-2026-43140 Référence CVE CVE-2026-43141 https://www.cve.org/CVERecord?id=CVE-2026-43141 Référence CVE CVE-2026-43147 https://www.cve.org/CVERecord?id=CVE-2026-43147 Référence CVE CVE-2026-43149 https://www.cve.org/CVERecord?id=CVE-2026-43149 Référence CVE CVE-2026-43152 https://www.cve.org/CVERecord?id=CVE-2026-43152 Référence CVE CVE-2026-43156 https://www.cve.org/CVERecord?id=CVE-2026-43156 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43159 https://www.cve.org/CVERecord?id=CVE-2026-43159 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43168 https://www.cve.org/CVERecord?id=CVE-2026-43168 Référence CVE CVE-2026-43171 https://www.cve.org/CVERecord?id=CVE-2026-43171 Référence CVE CVE-2026-43180 https://www.cve.org/CVERecord?id=CVE-2026-43180 Référence CVE CVE-2026-43183 https://www.cve.org/CVERecord?id=CVE-2026-43183 Référence CVE CVE-2026-43184 https://www.cve.org/CVERecord?id=CVE-2026-43184 Référence CVE CVE-2026-43187 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0665Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-31408 Référence CVE CVE-2026-31419 https://www.cve.org/CVERecord?id=CVE-2026-31419 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31684 https://www.cve.org/CVERecord?id=CVE-2026-31684 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31709 https://www.cve.org/CVERecord?id=CVE-2026-31709 Référence CVE CVE-2026-43020 https://www.cve.org/CVERecord?id=CVE-2026-43020 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43051 https://www.cve.org/CVERecord?id=CVE-2026-43051 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=CVE-2026-43158 Référence CVE CVE-2026-43163 https://www.cve.org/CVERecord?id=CVE-2026-43163 Référence CVE CVE-2026-43190 https://www.cve.org/CVERecord?id=CVE-2026-43190 Gestion détaillée du document le 29 mai 2026 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-015622LinuxのLinux Kernelにおける境界外書き込みに関する脆弱性

Linuxカーネルにおいて、xfsのリーフブロックに拡張属性（xattrs）を追加する際のfreemap調整に関する問題が修正されました。この問題は、freemapエントリがエントリ配列と重複する不整合な状態を引き起こし、ASSERTが失敗することでファイルシステムがシャットダウンしてしまう原因となっていました。具体的には、freemapの調整が不十分であったため、エントリ配列と空き領域の境界が重なり、無効な状態が発生していました。修正では、すべてのfreemapエントリを適切に調整し、エントリ配列と重複しないようにすることで、この問題を解決しています。

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.
Fix availability varies by product
Affected
Fixed
Linux: < 2.6.12, 5.10.252 ≤ 5.10.*, 5.15.202 ≤ 5.15.*, 6.1.165 ≤ 6.1.*, 6.6.128 ≤ 6.6.*, 6.12.75 ≤ 6.12.*, 6.18.16 ≤ 6.18.*, 6.19.6 ≤ 6.19.*, 7.0 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 6 May 2026 · Last source change 5 Aug 2026, 12:26 UTC · CWE-787 · Out-of-bounds Write

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-27719
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD enriched

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-27719↗Vendor CSAF · SUSE Product Security Team↗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-43158 · cve.blacktree.nl