Microsoft security update for CVE-2025-21791
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-21791. This page also shows what EchelonGraph holds for CVE-2025-21791, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products5
- azl3 kernel 6.6.78.1-3 on Azure Linux 3.0
- azl3 kernel 6.6.82.1-1 on Azure Linux 3.0
- cbl2 kernel 5.15.179.1-1 on CBL Mariner 2.0
- cbl2 kernel 5.15.182.1-1 on CBL Mariner 2.0
- cbl2 kernel 5.15.182.1-1 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 3 updates
3 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | — |
| — | Security Update | 5.15.179.1-1 |
| — | Security Update | 6.6.82.1-1 |
🧭 EchelonGraph on CVE-2025-21791
- EchelonGraph score
- 7.8 HIGH
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
In the Linux kernel, the following vulnerability has been resolved: vrf: use RCU protection in l3mdev_l3_out() l3mdev_l3_out() can be called without RCU being held: raw_sendmsg() ip_push_pending_frames() ip_send_skb() ip_local_out() __ip_local_out() l3mdev_ip_out() Add rcu_read_lock() / rcu_read_unlock() pair to avoid a potential UAF.
Published by kernel.org, the CVE Numbering Authority that assigned CVE-2025-21791, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).