CVE-2025-21669: Linux hwe edge · In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: discard packets if the transport changes If the socket has been
Affects linux-hwe-edgeSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 7.8 Medium · fixed in 5.15.0-1086.95~20.04.1 : update linux-hwe-edge when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.15.0-1086.95~20.04.1, 5.15.0-1081.90~20.04.1, 5.15.0-1080.87~20.04.1 +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 31 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| linux-hwe-edge | Affected
| Fixed in
|
AI-suggested
Red Hat has released updated kernel packages that address these vulnerabilities. Users should apply the kernel update as described in the advisory (https://access.redhat.com/articles/11258) and reboot their systems to ensure the fixes take effect. This is the official and recommended remediation. No additional mitigation steps are indicated by the vendor.
Description
In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: discard packets if the transport changes If the socket has been de-assigned or assigned to another transport, we must discard any packets received because they are not expected and would cause issues when we access vsk->transport. A possible scenario is described by Hyunwoo Kim in the attached link, where after a first connect() interrupted by a signal, and a second connect() failed, we can find `vsk->transport` at NULL, leading to a NULL pointer dereference.
References
- access.redhat.com/errata/RHSA-2025:8669 (opens in a new tab)
- access.redhat.com/security/updates/classification/ (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2343169 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2356587 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2357143 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2360300 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2367748 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_8669.json (opens in a new tab)
- ubuntu.com/security/CVE-2025-21669 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-21669 (opens in a new tab)
- git.kernel.org/linus/2cb7c756f605ec02ffe562fb26828e4bcc5fdfc1 (opens in a new tab)
- git.kernel.org/stable/c/18a7fc371d1dbf8deff16c2dd9292bcc73f43040 (opens in a new tab)
- git.kernel.org/stable/c/2cb7c756f605ec02ffe562fb26828e4bcc5fdfc1 (opens in a new tab)
- git.kernel.org/stable/c/6486915fa661584d70e8e7e4068c6c075c67dd6d (opens in a new tab)
- git.kernel.org/stable/c/677579b641af109613564460a4e3bdcb16850b61 (opens in a new tab)
- git.kernel.org/stable/c/88244163bc7e7b0ce9dd7bf4c8a563b41525c3ee (opens in a new tab)
- git.kernel.org/stable/c/d88b249e14bd0ee1e46bbe4f456e22e01b8c68de (opens in a new tab)
- ubuntu.com/security/notices/USN-7387-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7388-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7389-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7390-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7387-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7387-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-7407-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7421-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7445-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7448-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7458-1 (opens in a new tab)