Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2023-54121 on Ubuntu — linux

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix incorrect splitting in btrfs_drop_extent_map_range In production we were seeing a variety of WARN_ON()'s in the extent_map code, specifically in btrfs_drop_extent_map_range() when we have to call add_extent_mapping() for our second split. Consider the following extent map layout PINNED [0 16K) [32K, 48K) and then we call btrfs_drop_extent_map_range for [0, 36K), with skip_pinned == true. The initial loop will have start = 0 end = 36K len = 36K we will find the [0, 16k) extent, but since we are pinned we will skip it, which has this code start = em_end; if (end != (u64)-1) len = start + len - em_end; em_end here is 16K, so now the values are start = 16K len = 16K + 36K - 16K = 36K len should instead be 20K. This is a problem when we find the next extent at [32K, 48K), we need to split this extent to leave [36K, 48k), however the code for the split looks like this split->start = start + len; split->len = em_end - (start + len); In this case we have em_end = 48K split->start = 16K + 36K // this should be 16K + 20K split->len = 48K - (16K + 36K) // this overflows as 16K + 36K is 52K and now we have an invalid extent_map in the tree that potentially overlaps other entries in the extent map. Even in the non-overlapping case we will have split->start set improperly, which will cause problems with any block related calculations. We don't actually need len in this loop, we can simply use end as our end point, and only adjust start up when we find a pinned extent we need to skip. Adjust the logic to do this, which keeps us from inserting an invalid extent map. We only skip_pinned in the relocation case, so this is relatively rare, except in the case where you are running relocation a lot, which can happen with auto relocation on.

Distribution advisory

This page covers CVE-2023-54121 as tracked by Ubuntu, for the package linux. No fixed version has been recorded for this distribution yet.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: High — total loss, or loss the attacker controls.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

UBUNTU-CVE-2023-54121 is recorded against 124 packages.

  • linux
  • linux-allwinner-5.19
  • linux-aws
  • linux-aws-5.0
  • linux-aws-5.11
  • linux-aws-5.13
  • linux-aws-5.15
  • linux-aws-5.19
  • linux-aws-5.3
  • linux-aws-5.4
  • linux-aws-5.8
  • linux-aws-6.2
  • linux-aws-6.5
  • linux-aws-fips
  • linux-aws-hwe
  • linux-azure
  • linux-azure-4.15
  • linux-azure-5.11
  • linux-azure-5.13
  • linux-azure-5.15
  • linux-azure-5.19
  • linux-azure-5.3
  • linux-azure-5.4
  • linux-azure-5.8
Show the remaining 100 packages
  • linux-azure-6.11
  • linux-azure-6.2
  • linux-azure-6.5
  • linux-azure-edge
  • linux-azure-fde
  • linux-azure-fde-5.19
  • linux-azure-fde-6.2
  • linux-azure-fips
  • linux-bluefield
  • linux-fips
  • linux-gcp
  • linux-gcp-4.15
  • linux-gcp-5.11
  • linux-gcp-5.13
  • linux-gcp-5.15
  • linux-gcp-5.19
  • linux-gcp-5.3
  • linux-gcp-5.4
  • linux-gcp-5.8
  • linux-gcp-6.11
  • linux-gcp-6.2
  • linux-gcp-6.5
  • linux-gcp-fips
  • linux-gke
  • linux-gke-4.15
  • linux-gke-5.15
  • linux-gke-5.4
  • linux-gkeop
  • linux-gkeop-5.15
  • linux-gkeop-5.4
  • linux-hwe
  • linux-hwe-5.11
  • linux-hwe-5.13
  • linux-hwe-5.15
  • linux-hwe-5.19
  • linux-hwe-5.4
  • linux-hwe-5.8
  • linux-hwe-6.11
  • linux-hwe-6.2
  • linux-hwe-6.5
  • linux-hwe-edge
  • linux-ibm
  • linux-ibm-5.15
  • linux-ibm-5.4
  • linux-intel-5.13
  • linux-intel-iot-realtime
  • linux-intel-iotg
  • linux-intel-iotg-5.15
  • linux-iot
  • linux-kvm
  • linux-lowlatency
  • linux-lowlatency-hwe-5.15
  • linux-lowlatency-hwe-5.19
  • linux-lowlatency-hwe-6.11
  • linux-lowlatency-hwe-6.2
  • linux-lowlatency-hwe-6.5
  • linux-lts-xenial
  • linux-nvidia
  • linux-nvidia-6.11
  • linux-nvidia-6.2
  • linux-nvidia-6.5
  • linux-nvidia-tegra
  • linux-nvidia-tegra-5.15
  • linux-nvidia-tegra-igx
  • linux-oem
  • linux-oem-5.10
  • linux-oem-5.13
  • linux-oem-5.14
  • linux-oem-5.17
  • linux-oem-5.6
  • linux-oem-6.0
  • linux-oem-6.1
  • linux-oem-6.11
  • linux-oem-6.5
  • linux-oem-6.8
  • linux-oracle
  • linux-oracle-5.0
  • linux-oracle-5.11
  • linux-oracle-5.13
  • linux-oracle-5.15
  • linux-oracle-5.3
  • linux-oracle-5.4
  • linux-oracle-5.8
  • linux-oracle-6.5
  • linux-raspi
  • linux-raspi-5.4
  • linux-raspi-realtime
  • linux-raspi2
  • linux-realtime
  • linux-riscv
  • linux-riscv-5.11
  • linux-riscv-5.15
  • linux-riscv-5.19
  • linux-riscv-5.8
  • linux-riscv-6.14
  • linux-riscv-6.5
  • linux-starfive-5.19
  • linux-starfive-6.2
  • linux-starfive-6.5
  • linux-xilinx-zynqmp

Timeline and source

Published on 24 December 2025 and last revised on 19 August 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

ubuntu.com (Report)
www.cve.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)

Other advisories for this package

linux has other advisories on record. If you are patching this one, these are worth checking on the same host:

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-12-24
Updated 2026-08-20
Modified 2026-08-19
Fix URL N/A

Affected Packages

Software From version Fixed in
linux — —
linux-allwinner-5.19 — —
linux-aws — —
linux-aws-5.0 — —
linux-aws-5.11 — —
linux-aws-5.13 — —
linux-aws-5.15 — —
linux-aws-5.19 — —
linux-aws-5.3 — —
linux-aws-5.4 — —
linux-aws-5.8 — —
linux-aws-6.2 — —
linux-aws-6.5 — —
linux-aws-fips — —
linux-aws-hwe — —
linux-azure — —
linux-azure-4.15 — —
linux-azure-5.11 — —
linux-azure-5.13 — —
linux-azure-5.15 — —
linux-azure-5.19 — —
linux-azure-5.3 — —
linux-azure-5.4 — —
linux-azure-5.8 — —
linux-azure-6.11 — —
linux-azure-6.2 — —
linux-azure-6.5 — —
linux-azure-edge — —
linux-azure-fde — —
linux-azure-fde-5.19 — —
linux-azure-fde-6.2 — —
linux-azure-fips — —
linux-bluefield — —
linux-fips — —
linux-gcp — —
linux-gcp-4.15 — —
linux-gcp-5.11 — —
linux-gcp-5.13 — —
linux-gcp-5.15 — —
linux-gcp-5.19 — —
linux-gcp-5.3 — —
linux-gcp-5.4 — —
linux-gcp-5.8 — —
linux-gcp-6.11 — —
linux-gcp-6.2 — —
linux-gcp-6.5 — —
linux-gcp-fips — —
linux-gke — —
linux-gke-4.15 — —
linux-gke-5.15 — —
linux-gke-5.4 — —
linux-gkeop — —
linux-gkeop-5.15 — —
linux-gkeop-5.4 — —
linux-hwe — —
linux-hwe-5.11 — —
linux-hwe-5.13 — —
linux-hwe-5.15 — —
linux-hwe-5.19 — —
linux-hwe-5.4 — —
linux-hwe-5.8 — —
linux-hwe-6.11 — —
linux-hwe-6.2 — —
linux-hwe-6.5 — —
linux-hwe-edge — —
linux-ibm — —
linux-ibm-5.15 — —
linux-ibm-5.4 — —
linux-intel-5.13 — —
linux-intel-iot-realtime — —
linux-intel-iotg — —
linux-intel-iotg-5.15 — —
linux-iot — —
linux-kvm — —
linux-lowlatency — —
linux-lowlatency-hwe-5.15 — —
linux-lowlatency-hwe-5.19 — —
linux-lowlatency-hwe-6.11 — —
linux-lowlatency-hwe-6.2 — —
linux-lowlatency-hwe-6.5 — —
linux-lts-xenial — —
linux-nvidia — —
linux-nvidia-6.11 — —
linux-nvidia-6.2 — —
linux-nvidia-6.5 — —
linux-nvidia-tegra — —
linux-nvidia-tegra-5.15 — —
linux-nvidia-tegra-igx — —
linux-oem — —
linux-oem-5.10 — —
linux-oem-5.13 — —
linux-oem-5.14 — —
linux-oem-5.17 — —
linux-oem-5.6 — —
linux-oem-6.0 — —
linux-oem-6.1 — —
linux-oem-6.11 — —
linux-oem-6.5 — —
linux-oem-6.8 — —
linux-oracle — —
linux-oracle-5.0 — —
linux-oracle-5.11 — —
linux-oracle-5.13 — —
linux-oracle-5.15 — —
linux-oracle-5.3 — —
linux-oracle-5.4 — —
linux-oracle-5.8 — —
linux-oracle-6.5 — —
linux-raspi — —
linux-raspi-5.4 — —
linux-raspi-realtime — —
linux-raspi2 — —
linux-realtime — —
linux-riscv — —
linux-riscv-5.11 — —
linux-riscv-5.15 — —
linux-riscv-5.19 — —
linux-riscv-5.8 — —
linux-riscv-6.14 — —
linux-riscv-6.5 — —
linux-starfive-5.19 — —
linux-starfive-6.2 — —
linux-starfive-6.5 — —
linux-xilinx-zynqmp — —

Similar Threats

Site Security Check

Is linux part of your stack?

UBUNTU-CVE-2023-54121 is rated CVSS 7.8 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesUbuntuUbuntu 2023
✓