CyberSecBulletin
CVE-2025-39719NVD status: Modified

Linux: Out-of-bounds Read

Published Updated By the CyberSecBulletin desk

CVE-2025-39719 is a high-severity out-of-bounds read vulnerability in Linux, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions a0691ab6334f1769acc64ea9e319414a682ff45d, 50e823a23816b792daf6e8405f8d6045952bb90e, 4808ca3aa30ae857454d0b41d2d0bf161a312b45 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.16% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to a0691ab6334f1769acc64ea9e319414a682ff45d or 50e823a23816b792daf6e8405f8d6045952bb90e or 4808ca3aa30ae857454d0b41d2d0bf161a312b45 or 5c2b601922c064f7be70ae8621277f18d1ffec59, whichever matches your release line, or a later version.
  2. Update SIMATIC CN 4100 to V5.0 or a later version.
  3. Update Linux Kernel to 6.1.149 or 6.6.103 or 6.12.44 or 6.16.4, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux4aefe1c2bd0cb0223130671d459cd16efa3d3462 up to, but not including, a0691ab6334f1769acc64ea9e319414a682ff45d; 4aefe1c2bd0cb0223130671d459cd16efa3d3462 up to, but not including, 50e823a23816b792daf6e8405f8d6045952bb90e; 4aefe1c2bd0cb0223130671d459cd16efa3d3462 up to, but not including, 4808ca3aa30ae857454d0b41d2d0bf161a312b45; 4aefe1c2bd0cb0223130671d459cd16efa3d3462 up to, but not including, 5c2b601922c064f7be70ae8621277f18d1ffec59; 4aefe1c2bd0cb0223130671d459cd16efa3d3462 up to, but not including, 399b883ec828e436f1a721bf8551b4da8727e65b; 6.1a0691ab6334f1769acc64ea9e319414a682ff45d, 50e823a23816b792daf6e8405f8d6045952bb90e, 4808ca3aa30ae857454d0b41d2d0bf161a312b45, 5c2b601922c064f7be70ae8621277f18d1ffec59, 399b883ec828e436f1a721bf8551b4da8727e65b
SiemensSIMATIC CN 4100before V5.0V5.0
LinuxLinux Kernel6.1 up to, but not including, 6.1.149; 6.2 up to, but not including, 6.6.103; 6.7 up to, but not including, 6.12.44; 6.13 up to, but not including, 6.16.46.1.149, 6.6.103, 6.12.44, 6.16.4
DebianDebian Linux11.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H. Scored by NVD.

Official description

In the Linux kernel, the following vulnerability has been resolved: iio: imu: bno055: fix OOB access of hw_xlate array Fix a potential out-of-bounds array access of the hw_xlate array in bno055.c. In bno055_get_regmask(), hw_xlate was iterated over the length of the vals array instead of the length of the hw_xlate array. In the case of bno055_gyr_scale, the vals array is larger than the hw_xlate array, so this could result in an out-of-bounds access. In practice, this shouldn't happen though because a match should always be found which breaks out of the for loop before it iterates beyond the end of the hw_xlate array. By adding a new hw_xlate_len field to the bno055_sysfs_attr, we can be sure we are iterating over the correct length.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Read

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

How developers prevent this class of flaw

  • Use a language that provides appropriate memory abstractions.

More Out-of-bounds Read vulnerabilities (CWE-125)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Recent Out-of-bounds Read vulnerabilities

Spotted an error? Tell us.