Red Hat Enterprise Linux 10: Write-what-where Condition
CVE-2025-9900 is a high-severity write-what-where condition vulnerability in Red Hat Enterprise Linux 10 from Red Hat, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. There is no confirmed exploitation so far. EPSS estimates a 1% chance of exploitation within 30 days, higher than 64% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Red Hat Enterprise Linux 10 you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CNA (redhat.com).
Official description
A flaw was found in Libtiff. This vulnerability is a "write-what-where" condition, triggered when the library processes a specially crafted TIFF image file. By providing an abnormally large image height value in the file's metadata, an attacker can trick the library into writing attacker-controlled color data to an arbitrary memory location. This memory corruption can be exploited to cause a denial of service (application crash) or to achieve arbitrary code execution with the permissions of the user.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Write-what-where Condition
Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.
How developers prevent this class of flaw
- Use a language that provides appropriate memory abstractions.
- Use OS-level preventative functionality integrated after the fact. Not a complete solution.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
- access.redhat.com/errata/RHSA-2025:17651
- access.redhat.com/errata/RHSA-2025:17675
- access.redhat.com/errata/RHSA-2025:17710
- access.redhat.com/errata/RHSA-2025:17738
- access.redhat.com/errata/RHSA-2025:17739
- access.redhat.com/errata/RHSA-2025:17740
- access.redhat.com/errata/RHSA-2025:19113
- access.redhat.com/errata/RHSA-2025:19156
- access.redhat.com/errata/RHSA-2025:19276
- access.redhat.com/errata/RHSA-2025:19906
- access.redhat.com/errata/RHSA-2025:19947
- access.redhat.com/errata/RHSA-2025:20956
- access.redhat.com/errata/RHSA-2025:20998
- access.redhat.com/errata/RHSA-2025:21060
- access.redhat.com/errata/RHSA-2025:21061
Other vulnerabilities in Red Hat Enterprise Linux 10
- 8.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.9 High severity
- 7.3 High severity
- 7.5 High severity
Recent Write-what-where Condition vulnerabilities
- 8.8 High severity
- 7.8 High severity
- 8.2 High severity
- 8.1 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.