CVE-2025-38273: net: tipc: fix refcount warning in tipc_aead_encrypt

Published Jul 10, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

net: tipc: fix refcount warning in tipcaeadencrypt

syzbot reported a refcount warning [1] caused by calling getnet() 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 getnet() call in commit e279024617134 ("net/tipc: fix slab-use-after-free Read in tipcaeadencryptdone") 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 getnet() with maybegetnet(), 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/68342b55.a70a0220.253bc2.0091.GAE@google.com/T/#m12019cf9ae77e1954f666914640efa36d52704a2

Affected Software

11 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=6.12.31<6.12.34
Linux Linux kernel>=6.14.9<6.15
Linux Linux kernel>=6.15.1<6.15.3
Linux Linux kernel=5.10.238
Linux Linux kernel=5.15.185
Linux Linux kernel=6.1.141
Linux Linux kernel=6.6.93
Linux Linux kernel=6.15
Debian Debian Linux=11.0
debian/linux
6.1.176-16.1.190-16.12.107-16.12.113-17.2.12-17.2.13-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1

Event History

Jul 10, 2025
CVE Published
via MITRE·07:41 AM
Data Sourced
via MITRE·07:41 AM
DescriptionSeverity
Data Sourced
via NVD·08:15 AM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2025-38273?

CVE-2025-38273 has been categorized as a medium severity vulnerability due to the risk of refcount warnings that could lead to instability.

2

How do I fix CVE-2025-38273?

To fix CVE-2025-38273, update your Linux kernel to the latest stable version that contains the patch addressing this issue.

3

Which Linux kernel versions are affected by CVE-2025-38273?

CVE-2025-38273 affects Linux kernel versions between 5.10.238 and 6.15, along with specific later versions.

4

What type of vulnerability is CVE-2025-38273?

CVE-2025-38273 is a reference counting error related to the TIPC protocol in the Linux kernel.

5

Can CVE-2025-38273 be exploited remotely?

CVE-2025-38273 is not categorized as a remote exploit but may impact system stability if a vulnerable kernel is running.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203