Security readout for executives and security teams
Plain-English summary
CVE-2025-39900 is a Linux kernel availability issue in the traffic control estimator path. On kernels built with CONFIG_PREEMPT_RT, a timer callback can be preempted in a way that triggers a kernel warning. The reported impact is local denial of service, not data theft or remote compromise.
Executive priority
Treat as a routine but time-bound kernel maintenance item. It is not presented as remotely exploitable or actively exploited, but availability impact can matter on shared or real-time Linux infrastructure. Patch through normal kernel update channels, prioritizing systems with local multi-user exposure.
Technical view
The flaw is in net/core/gen_estimator.c est_timer(). With CONFIG_PREEMPT_RT=y, timer callbacks can be preempted, violating seqlock expectations and causing a syzbot-reported WARNING. The upstream fix adopts preempt_disable_nested() and preempt_enable_nested(). CVSS is 5.5: local, low complexity, low privilege, no user interaction, high availability impact.
Likely exposure
Exposure appears limited to Linux systems running affected kernel versions or downstream builds, especially real-time kernels with CONFIG_PREEMPT_RT enabled and net scheduler estimator code reachable. The source bundle lists Linux 6.12, 6.12.46, 6.16.6, and 6.17 as affected entries, but distro backport status is not provided.
Exploitation context
The bundle shows no KEV listing and no cited evidence of active exploitation. The CVSS vector requires local low-privileged access. Impact is availability only, so risk is higher on shared hosts, CI runners, appliances, or real-time systems where local users or workloads are less trusted.
Researcher notes
Evidence is strongest for the root cause and upstream fix direction. The bundle does not include exploit details, distro package names, or complete fixed version ranges. Validate exposure through kernel configuration, vendor backport metadata, and whether the stable commits are present in the deployed kernel tree.
Mitigation direction
Apply a vendor kernel update containing the referenced stable fixes.
Prioritize systems using CONFIG_PREEMPT_RT or real-time kernel packages.
Check distribution advisories for backported fixes before assuming version safety.
Limit unnecessary local user and container access until patched.
Monitor Linux stable references for branch-specific correction status.
Validation and detection
Inventory running kernel versions across Linux hosts.
Check whether kernels are built with CONFIG_PREEMPT_RT enabled.
Compare installed kernels against vendor advisories and referenced stable commits.
Confirm patched hosts no longer match affected vendor package versions.
Review shared systems for untrusted local users or workloads.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-39900 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.