Linux: Out-of-bounds Read
CVE-2025-38679 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 a3eef5847603cd8a4110587907988c3f93c9605a, 8f274e2b05fdae7a53cee83979202b5ecb49035c, 6f08bfb5805637419902f3d70069fe17a404545b 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.17% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to a3eef5847603cd8a4110587907988c3f93c9605a or 8f274e2b05fdae7a53cee83979202b5ecb49035c or 6f08bfb5805637419902f3d70069fe17a404545b or c956c3758510b448b3d4d10d1da8230e8c9bf668, whichever matches your release line, or a later version.
- Update SIMATIC CN 4100 to V5.0 or a later version.
- Update Linux Kernel to 6.1.149 or 6.6.103 or 6.12.43 or 6.15.11, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | 09c2845e8fe4fcab942929480203f504a6e0a114 up to, but not including, a3eef5847603cd8a4110587907988c3f93c9605a; 09c2845e8fe4fcab942929480203f504a6e0a114 up to, but not including, 8f274e2b05fdae7a53cee83979202b5ecb49035c; 09c2845e8fe4fcab942929480203f504a6e0a114 up to, but not including, 6f08bfb5805637419902f3d70069fe17a404545b; 09c2845e8fe4fcab942929480203f504a6e0a114 up to, but not including, c956c3758510b448b3d4d10d1da8230e8c9bf668; 09c2845e8fe4fcab942929480203f504a6e0a114 up to, but not including, bed4921055dd7bb4d2eea2729852ae18cf97a2c6; 09c2845e8fe4fcab942929480203f504a6e0a114 up to, but not including, 06d6770ff0d8cc8dfd392329a8cc03e2a83e7289; 4.13 | a3eef5847603cd8a4110587907988c3f93c9605a, 8f274e2b05fdae7a53cee83979202b5ecb49035c, 6f08bfb5805637419902f3d70069fe17a404545b, c956c3758510b448b3d4d10d1da8230e8c9bf668, bed4921055dd7bb4d2eea2729852ae18cf97a2c6, 06d6770ff0d8cc8dfd392329a8cc03e2a83e7289 |
| Siemens | SIMATIC CN 4100 | before V5.0 | V5.0 |
| Linux | Linux Kernel | 4.13 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.43; 6.13 up to, but not including, 6.15.11; 6.16 up to, but not including, 6.16.2 | 6.1.149, 6.6.103, 6.12.43, 6.15.11, 6.16.2 |
| Debian | Debian Linux | 11.0 | Not 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.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.3 | High | CNA |
| CVSS 3.1 | 7.1 | High | NVD |
Official description
In the Linux kernel, the following vulnerability has been resolved: media: venus: Fix OOB read due to missing payload bound check Currently, The event_seq_changed() handler processes a variable number of properties sent by the firmware. The number of properties is indicated by the firmware and used to iterate over the payload. However, the payload size is not being validated against the actual message length. This can lead to out-of-bounds memory access if the firmware provides a property count that exceeds the data available in the payload. Such a condition can result in kernel crashes or potential information leaks if memory beyond the buffer is accessed. Fix this by properly validating the remaining size of the payload before each property access and updating bounds accordingly as properties are parsed. This ensures that property parsing is safely bounded within the received message buffer and protects against malformed or malicious firmware behavior.
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.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- git.kernel.org/stable/c/06d6770ff0d8cc8dfd392329a8cc03e2a83e7289
- git.kernel.org/stable/c/6f08bfb5805637419902f3d70069fe17a404545b
- git.kernel.org/stable/c/8f274e2b05fdae7a53cee83979202b5ecb49035c
- git.kernel.org/stable/c/a3eef5847603cd8a4110587907988c3f93c9605a
- git.kernel.org/stable/c/bed4921055dd7bb4d2eea2729852ae18cf97a2c6
- git.kernel.org/stable/c/c956c3758510b448b3d4d10d1da8230e8c9bf668
Third-party and government advisories
- lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlThird Party Advisory
Other references
Recent Out-of-bounds Read vulnerabilities
- 8.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
- 7.1 High severity
Spotted an error? Tell us.