BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2023-54285High confidence

iomap: Fix possible overflow condition in iomap_write_delalloc_scan

Linux · Linux

7.1HighCVSS 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 9 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:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.18% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • 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: As exposure requiresRemediation target: Within 365 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 9 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.

13 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 9 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.5.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.162-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.5.6-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-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-gcp-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-hwe-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-lowlatency-hwe-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-nvidia-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-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-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
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-2023-54285 · CSAF 2.0 · revision 34 · interimSUSE Product Security TeamCVE-2023-54285
15 known affected

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

  • SLES 15 SP1 CHOST Images for Amazon EC2
  • SLES 15 SP2 CHOST Images for Amazon EC2
  • SLES 15 SP3 CHOST Images for Amazon EC2
  • SLES 15 SP4 CHOST Images for Amazon EC2
  • SLES 15 SP5 CHOST Images for Amazon EC2
  • SLES 15 SP1 CHOST Images for Google
  • SLES 15 SP2 CHOST Images for Google
  • SLES 15 SP3 CHOST Images for Google
  • SLES 15 SP4 CHOST Images for Google
  • SLES 15 SP5 CHOST Images for Google
  • SLES 15 SP1 CHOST Images for Microsoft Azure
  • SLES 15 SP2 CHOST Images for Microsoft Azure
Summary
In the Linux kernel, the following vulnerability has been resolved: iomap: Fix possible overflow condition in iomap_write_delalloc_scan folio_next_index() returns an unsigned long value which left shifted by PAGE_SHIFT could possibly cause an overflow on 32-bit system. Instead use folio_pos(folio) + folio_size(folio), which does this correctly.
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-2023-60519

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 9 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: iomap: Fix possible overflow condition in iomap_write_delalloc_scan folio_next_index() returns an unsigned long value which left shifted by PAGE_SHIFT could possibly cause an overflow on 32-bit system. Instead use folio_pos(folio) + folio_size(folio), which does this correctly.

What

In the Linux kernel, the following vulnerability has been resolved: iomap: Fix possible overflow condition in iomap_write_delalloc_scan folio_next_index() returns an unsigned long value which left shifted by PAGE_SHIFT could possibly cause an overflow on 32-bit system. Instead use folio_pos(folio) + folio_size(folio), which does this correctly.

Why

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

How

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

What

In the Linux kernel, the following vulnerability has been resolved: iomap: Fix possible overflow condition in iomap_write_delalloc_scan folio_next_index() returns an unsigned long value which left shifted by PAGE_SHIFT could possibly cause an overflow on 32-bit system. Instead use folio_pos(folio) + folio_size(folio), which does this correctly.

Why

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

How

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

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
local access → Out-of-bounds Write → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: 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:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

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

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.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
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-787
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-2941Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein Angreifer kann diese Schwachstellen ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu Denial‑of‑Service, Speicherbeschädigung oder weiteren nicht definierten Auswirkungen führen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251231Security Bulletin 31 Dec 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 31 Dec 2025, published on 31 December 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2023-54264 Référence CVE CVE-2023-54266 https://www.cve.org/CVERecord?id=CVE-2023-54266 Référence CVE CVE-2023-54267 https://www.cve.org/CVERecord?id=CVE-2023-54267 Référence CVE CVE-2023-54271 https://www.cve.org/CVERecord?id=CVE-2023-54271 Référence CVE CVE-2023-54276 https://www.cve.org/CVERecord?id=CVE-2023-54276 Référence CVE CVE-2023-54278 https://www.cve.org/CVERecord?id=CVE-2023-54278 Référence CVE CVE-2023-54281 https://www.cve.org/CVERecord?id=CVE-2023-54281 Référence CVE CVE-2023-54282 https://www.cve.org/CVERecord?id=CVE-2023-54282 Référence CVE CVE-2023-54283 https://www.cve.org/CVERecord?id=CVE-2023-54283 Référence CVE CVE-2023-54285 https://www.cve.org/CVERecord?id=CVE-2023-54285 Référence CVE CVE-2023-54289 https://www.cve.org/CVERecord?id=CVE-2023-54289 Référence CVE CVE-2023-54291 https://www.cve.org/CVERecord?id=CVE-2023-54291 Référence CVE CVE-2023-54292 https://www.cve.org/CVERecord?id=CVE-2023-54292 Référence CVE CVE-2023-54293 https://www.cve.org/CVERecord?id=CVE-2023-54293 Référence CVE CVE-2023-54296 https://www.cve.org/CVERecord?id=CVE-2023-54296 Référence CVE CVE-2023-54297 https://www.cve.org/CVERecord?id=CVE-2023-54297 Référence CVE CVE-2023-54299 https://www.cve.org/CVERecord?id=CVE-2023-54299 Référence CVE CVE-2023-54300 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-54237 Référence CVE CVE-2023-54242 https://www.cve.org/CVERecord?id=CVE-2023-54242 Référence CVE CVE-2023-54247 https://www.cve.org/CVERecord?id=CVE-2023-54247 Référence CVE CVE-2023-54253 https://www.cve.org/CVERecord?id=CVE-2023-54253 Référence CVE CVE-2023-54259 https://www.cve.org/CVERecord?id=CVE-2023-54259 Référence CVE CVE-2023-54261 https://www.cve.org/CVERecord?id=CVE-2023-54261 Référence CVE CVE-2023-54263 https://www.cve.org/CVERecord?id=CVE-2023-54263 Référence CVE CVE-2023-54271 https://www.cve.org/CVERecord?id=CVE-2023-54271 Référence CVE CVE-2023-54280 https://www.cve.org/CVERecord?id=CVE-2023-54280 Référence CVE CVE-2023-54285 https://www.cve.org/CVERecord?id=CVE-2023-54285 Référence CVE CVE-2023-54320 https://www.cve.org/CVERecord?id=CVE-2023-54320 Référence CVE CVE-2023-54323 https://www.cve.org/CVERecord?id=CVE-2023-54323 Référence CVE CVE-2023-54324 https://www.cve.org/CVERecord?id=CVE-2023-54324 Référence CVE CVE-2023-5678 https://www.cve.org/CVERecord?id=CVE-2023-5678 Référence CVE CVE-2023-6129 https://www.cve.org/CVERecord?id=CVE-2023-6129 Référence CVE CVE-2023-6237 https://www.cve.org/CVERecord?id=CVE-2023-6237 Référence CVE CVE-2023-6240 https://www.cve.org/CVERecord?id=CVE-2023-6240 Référence CVE CVE-2023-6610 https://www.cve.org/CVERecord?id=CVE-2023-

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

d?id=CVE-2023-54237 Référence CVE CVE-2023-54242 https://www.cve.org/CVERecord?id=CVE-2023-54242 Référence CVE CVE-2023-54247 https://www.cve.org/CVERecord?id=CVE-2023-54247 Référence CVE CVE-2023-54253 https://www.cve.org/CVERecord?id=CVE-2023-54253 Référence CVE CVE-2023-54259 https://www.cve.org/CVERecord?id=CVE-2023-54259 Référence CVE CVE-2023-54261 https://www.cve.org/CVERecord?id=CVE-2023-54261 Référence CVE CVE-2023-54263 https://www.cve.org/CVERecord?id=CVE-2023-54263 Référence CVE CVE-2023-54271 https://www.cve.org/CVERecord?id=CVE-2023-54271 Référence CVE CVE-2023-54280 https://www.cve.org/CVERecord?id=CVE-2023-54280 Référence CVE CVE-2023-54285 https://www.cve.org/CVERecord?id=CVE-2023-54285 Référence CVE CVE-2023-54320 https://www.cve.org/CVERecord?id=CVE-2023-54320 Référence CVE CVE-2023-54323 https://www.cve.org/CVERecord?id=CVE-2023-54323 Référence CVE CVE-2023-54324 https://www.cve.org/CVERecord?id=CVE-2023-54324 Référence CVE CVE-2023-5678 https://www.cve.org/CVERecord?id=CVE-2023-5678 Référence CVE CVE-2023-6129 https://www.cve.org/CVERecord?id=CVE-2023-6129 Référence CVE CVE-2023-6237 https://www.cve.org/CVERecord?id=CVE-2023-6237 Référence CVE CVE-2023-6240 https://www.cve.org/CVERecord?id=CVE-2023-6240 Référence CVE CVE-2023-6610 https://www.cve.org/CVERecord?id=CVE-2023-

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

d?id=CVE-2023-54264 Référence CVE CVE-2023-54266 https://www.cve.org/CVERecord?id=CVE-2023-54266 Référence CVE CVE-2023-54267 https://www.cve.org/CVERecord?id=CVE-2023-54267 Référence CVE CVE-2023-54271 https://www.cve.org/CVERecord?id=CVE-2023-54271 Référence CVE CVE-2023-54276 https://www.cve.org/CVERecord?id=CVE-2023-54276 Référence CVE CVE-2023-54278 https://www.cve.org/CVERecord?id=CVE-2023-54278 Référence CVE CVE-2023-54281 https://www.cve.org/CVERecord?id=CVE-2023-54281 Référence CVE CVE-2023-54282 https://www.cve.org/CVERecord?id=CVE-2023-54282 Référence CVE CVE-2023-54283 https://www.cve.org/CVERecord?id=CVE-2023-54283 Référence CVE CVE-2023-54285 https://www.cve.org/CVERecord?id=CVE-2023-54285 Référence CVE CVE-2023-54289 https://www.cve.org/CVERecord?id=CVE-2023-54289 Référence CVE CVE-2023-54291 https://www.cve.org/CVERecord?id=CVE-2023-54291 Référence CVE CVE-2023-54292 https://www.cve.org/CVERecord?id=CVE-2023-54292 Référence CVE CVE-2023-54293 https://www.cve.org/CVERecord?id=CVE-2023-54293 Référence CVE CVE-2023-54296 https://www.cve.org/CVERecord?id=CVE-2023-54296 Référence CVE CVE-2023-54297 https://www.cve.org/CVERecord?id=CVE-2023-54297 Référence CVE CVE-2023-54299 https://www.cve.org/CVERecord?id=CVE-2023-54299 Référence CVE CVE-2023-54300 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-54275 Référence CVE CVE-2023-54276 https://www.cve.org/CVERecord?id=CVE-2023-54276 Référence CVE CVE-2023-54277 https://www.cve.org/CVERecord?id=CVE-2023-54277 Référence CVE CVE-2023-54278 https://www.cve.org/CVERecord?id=CVE-2023-54278 Référence CVE CVE-2023-54280 https://www.cve.org/CVERecord?id=CVE-2023-54280 Référence CVE CVE-2023-54281 https://www.cve.org/CVERecord?id=CVE-2023-54281 Référence CVE CVE-2023-54282 https://www.cve.org/CVERecord?id=CVE-2023-54282 Référence CVE CVE-2023-54283 https://www.cve.org/CVERecord?id=CVE-2023-54283 Référence CVE CVE-2023-54284 https://www.cve.org/CVERecord?id=CVE-2023-54284 Référence CVE CVE-2023-54285 https://www.cve.org/CVERecord?id=CVE-2023-54285 Référence CVE CVE-2023-54286 https://www.cve.org/CVERecord?id=CVE-2023-54286 Référence CVE CVE-2023-54287 https://www.cve.org/CVERecord?id=CVE-2023-54287 Référence CVE CVE-2023-54289 https://www.cve.org/CVERecord?id=CVE-2023-54289 Référence CVE CVE-2023-54291 https://www.cve.org/CVERecord?id=CVE-2023-54291 Référence CVE CVE-2023-54292 https://www.cve.org/CVERecord?id=CVE-2023-54292 Référence CVE CVE-2023-54293 https://www.cve.org/CVERecord?id=CVE-2023-54293 Référence CVE CVE-2023-54294 https://www.cve.org/CVERecord?id=CVE-2023-54294 Référence CVE CVE-2023-54295 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2022-48744 Référence CVE CVE-2022-49168 https://www.cve.org/CVERecord?id=CVE-2022-49168 Référence CVE CVE-2022-49465 https://www.cve.org/CVERecord?id=CVE-2022-49465 Référence CVE CVE-2022-49711 https://www.cve.org/CVERecord?id=CVE-2022-49711 Référence CVE CVE-2022-49743 https://www.cve.org/CVERecord?id=CVE-2022-49743 Référence CVE CVE-2023-52658 https://www.cve.org/CVERecord?id=CVE-2023-52658 Référence CVE CVE-2023-52975 https://www.cve.org/CVERecord?id=CVE-2023-52975 Référence CVE CVE-2023-53421 https://www.cve.org/CVERecord?id=CVE-2023-53421 Référence CVE CVE-2023-54207 https://www.cve.org/CVERecord?id=CVE-2023-54207 Référence CVE CVE-2023-54285 https://www.cve.org/CVERecord?id=CVE-2023-54285 Référence CVE CVE-2023-54321 https://www.cve.org/CVERecord?id=CVE-2023-54321 Référence CVE CVE-2024-36903 https://www.cve.org/CVERecord?id=CVE-2024-36903 Référence CVE CVE-2024-36927 https://www.cve.org/CVERecord?id=CVE-2024-36927 Référence CVE CVE-2024-42079 https://www.cve.org/CVERecord?id=CVE-2024-42079 Référence CVE CVE-2024-46786 https://www.cve.org/CVERecord?id=CVE-2024-46786 Référence CVE CVE-2024-49968 https://www.cve.org/CVERecord?id=CVE-2024-49968 Référence CVE CVE-2025-21946 https://www.cve.org/CVERecord?id=CVE-2025-21946 Référence CVE CVE-2025-22022 https://www.cve.org/CVERecord?id=

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

élévation de privilèges, une atteinte à la confidentialité des données et un déni de service. Solutions Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Debian DSA-6126-1 du 09 février 2026 https://lists.debian.org/debian-security-announce/2026/msg00035.html Bulletin de sécurité Debian DSA-6127-1 du 09 février 2026 https://lists.debian.org/debian-security-announce/2026/msg00036.html Référence CVE CVE-2023-52658 https://www.cve.org/CVERecord?id=CVE-2023-52658 Référence CVE CVE-2023-53421 https://www.cve.org/CVERecord?id=CVE-2023-53421 Référence CVE CVE-2023-54285 https://www.cve.org/CVERecord?id=CVE-2023-54285 Référence CVE CVE-2024-42079 https://www.cve.org/CVERecord?id=CVE-2024-42079 Référence CVE CVE-2024-46786 https://www.cve.org/CVERecord?id=CVE-2024-46786 Référence CVE CVE-2024-49968 https://www.cve.org/CVERecord?id=CVE-2024-49968 Référence CVE CVE-2024-58096 https://www.cve.org/CVERecord?id=CVE-2024-58096 Référence CVE CVE-2024-58097 https://www.cve.org/CVERecord?id=CVE-2024-58097 Référence CVE CVE-2025-21946 https://www.cve.org/CVERecord?id=CVE-2025-21946 Référence CVE CVE-2025-22022 https://www.cve.org/CVERecord?id=CVE-2025-22022 Référence CVE CVE-2025-22083 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-54275 Référence CVE CVE-2023-54276 https://www.cve.org/CVERecord?id=CVE-2023-54276 Référence CVE CVE-2023-54277 https://www.cve.org/CVERecord?id=CVE-2023-54277 Référence CVE CVE-2023-54278 https://www.cve.org/CVERecord?id=CVE-2023-54278 Référence CVE CVE-2023-54280 https://www.cve.org/CVERecord?id=CVE-2023-54280 Référence CVE CVE-2023-54281 https://www.cve.org/CVERecord?id=CVE-2023-54281 Référence CVE CVE-2023-54282 https://www.cve.org/CVERecord?id=CVE-2023-54282 Référence CVE CVE-2023-54283 https://www.cve.org/CVERecord?id=CVE-2023-54283 Référence CVE CVE-2023-54284 https://www.cve.org/CVERecord?id=CVE-2023-54284 Référence CVE CVE-2023-54285 https://www.cve.org/CVERecord?id=CVE-2023-54285 Référence CVE CVE-2023-54286 https://www.cve.org/CVERecord?id=CVE-2023-54286 Référence CVE CVE-2023-54287 https://www.cve.org/CVERecord?id=CVE-2023-54287 Référence CVE CVE-2023-54289 https://www.cve.org/CVERecord?id=CVE-2023-54289 Référence CVE CVE-2023-54291 https://www.cve.org/CVERecord?id=CVE-2023-54291 Référence CVE CVE-2023-54292 https://www.cve.org/CVERecord?id=CVE-2023-54292 Référence CVE CVE-2023-54293 https://www.cve.org/CVERecord?id=CVE-2023-54293 Référence CVE CVE-2023-54294 https://www.cve.org/CVERecord?id=CVE-2023-54294 Référence CVE CVE-2023-54295 https://www.cve.org/CVERecord?id=

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

Linuxカーネルにおいて、以下の脆弱性が修正されました。iomap_write_delalloc_scan関数におけるオーバーフローの可能性のある条件を修正しました。folio_next_index()は符号なしlong値を返しますが、これをPAGE_SHIFT分左シフトすると32ビットシステムでオーバーフローを引き起こす可能性があります。代わりに、folio_pos(folio) + folio_size(folio)を使用してください。こちらの方法で正しく処理されます。

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: < 6.2, 6.1.162 ≤ 6.1.*, 6.5.5 ≤ 6.5.*, 6.6 ≤ *
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. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 30 Dec 2025 · Last source change 5 Aug 2026, 09:18 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-2023-60519
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
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
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-2023-54285 · cve.blacktree.nl