Answer in brief
CVE-2025-38273 records a Unknown severity vulnerability in net: tipc: fix refcount warning in tipc_aead_encrypt. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-38273 records a Unknown severity vulnerability in net: tipc: fix refcount warning in tipc_aead_encrypt. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d42ed4de6aba232d946d20653a70f79158a6535b <445d59025d76d0638b03110f8791d5b89ed5162d || >=f5c2c4eaaa5a8e7e0685ec031d480e588e263e59 <e0b11227c4e8eb4bdf1b86aa8f0f3abb24e0f029 || >=b8fcae6d2e93c54cacb8f579a77d827c1c643eb5 <307391e8fe70401a6d39ecc9978e13c2c0cdf81f || >=b19fc1d0be3c3397e5968fe2627f22e7f84673b1 <acab7ca5ff19889b80a8ee7dec220ee1a96dede9 || >=689a205cd968a1572ab561b0c4c2d50a10e9d3b0 <c762fc79d710d676b793f9d98b1414efe6eb51e6 || >=e279024617134c94fd3e37470156534d5f2b3472 <9ff60e0d9974dccf24e89bcd3ee7933e538d929f || >=e279024617134c94fd3e37470156534d5f2b3472 <f29ccaa07cf3d35990f4d25028cc55470d29372b || 4a0fddc2c0d5c28aec8c262ad4603be0bef1938c || >=5.10.238 <5.10.239 || >=5.15.185 <5.15.186 || >=6.1.141 <6.1.142 || >=6.6.93 <6.6.94 || >=6.12.31 <6.12.34 || >=6.14.9 <6.15 | 445d59025d76d0638b03110f8791d5b89ed5162d, e0b11227c4e8eb4bdf1b86aa8f0f3abb24e0f029, 307391e8fe70401a6d39ecc9978e13c2c0cdf81f, acab7ca5ff19889b80a8ee7dec220ee1a96dede9, c762fc79d710d676b793f9d98b1414efe6eb51e6, 9ff60e0d9974dccf24e89bcd3ee7933e538d929f, f29ccaa07cf3d35990f4d25028cc55470d29372b, 5.10.239, 5.15.186, 6.1.142, 6.6.94, 6.12.34, 6.15 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Jul 10, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: net: tipc: fix refcount warning in tipc_aead_encrypt syzbot reported a refcount warning [1] caused by calling get_net() on a network namespace that is being destroyed (refcount=0). This happens when a TIPC discovery timer fires during network namespace cleanup. The recently added get_net() call in commit e279024617134 ("net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done") attempts to hold a reference to the network namespace. However, if the namespace is already being destroyed, its refcount might be zero, leading to the use-after-free warning. Replace get_net() with maybe_get_net(), which safely checks if the refcount is non-zero before incrementing it. If the namespace is being destroyed, return -ENODEV early, after releasing the bearer reference. [1]: https://lore.kernel.org/all/[email protected]/T/#m12019cf9ae77e1954f666914640efa36d52704a2
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=d42ed4de6aba232d946d20653a70f79158a6535b <445d59025d76d0638b03110f8791d5b89ed5162d || >=f5c2c4eaaa5a8e7e0685ec031d480e588e263e59 <e0b11227c4e8eb4bdf1b86aa8f0f3abb24e0f029 || >=b8fcae6d2e93c54cacb8f579a77d827c1c643eb5 <307391e8fe70401a6d39ecc9978e13c2c0cdf81f || >=b19fc1d0be3c3397e5968fe2627f22e7f84673b1 <acab7ca5ff19889b80a8ee7dec220ee1a96dede9 || >=689a205cd968a1572ab561b0c4c2d50a10e9d3b0 <c762fc79d710d676b793f9d98b1414efe6eb51e6 || >=e279024617134c94fd3e37470156534d5f2b3472 <9ff60e0d9974dccf24e89bcd3ee7933e538d929f || >=e279024617134c94fd3e37470156534d5f2b3472 <f29ccaa07cf3d35990f4d25028cc55470d29372b || 4a0fddc2c0d5c28aec8c262ad4603be0bef1938c || >=5.10.238 <5.10.239 || >=5.15.185 <5.15.186 || >=6.1.141 <6.1.142 || >=6.6.93 <6.6.94 || >=6.12.31 <6.12.34 || >=6.14.9 <6.15 | 445d59025d76d0638b03110f8791d5b89ed5162d, e0b11227c4e8eb4bdf1b86aa8f0f3abb24e0f029, 307391e8fe70401a6d39ecc9978e13c2c0cdf81f, acab7ca5ff19889b80a8ee7dec220ee1a96dede9, c762fc79d710d676b793f9d98b1414efe6eb51e6, 9ff60e0d9974dccf24e89bcd3ee7933e538d929f, f29ccaa07cf3d35990f4d25028cc55470d29372b, 5.10.239, 5.15.186, 6.1.142, 6.6.94, 6.12.34, 6.15 |
| Linux/Linuxgeneric | 6.15 | Not reported |
Published upstream
Jul 10, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: net: tipc: fix refcount warning in tipc_aead_encrypt syzbot reported a refcount warning [1] caused by calling get_net() on a network namespace that is being destroyed (refcount=0). This happens when a TIPC discovery timer fires during network namespace cleanup. The recently added get_net() call in commit e279024617134 ("net/tipc: fix slab-use-after-free Read in tipc_aead_encrypt_done") attempts to hold a reference to the network namespace. However, if the namespace is already being destroyed, its refcount might be zero, leading to the use-after-free warning. Replace get_net() with maybe_get_net(), which safely checks if the refcount is non-zero before incrementing it. If the namespace is being destroyed, return -ENODEV early, after releasing the bearer reference. [1]: https://lore.kernel.org/all/[email protected]/T/#m12019cf9ae77e1954f666914640efa36d52704a2
Quoted source text, attributed separately from HOL analysis.