CVE-2025-21646
Last modified
CVE-2025-21646 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: afs: Fix the maximum cell name length The kafs filesystem limits the maximum length of a cell to 256 bytes, but a problem occurs if someone actually does that: kafs tries to create a directory under /proc/net/afs/ with the name of the cell, but that fails with a warning: WARNING: CPU: 0 PID: 9 at fs/proc/generic.c:405 because procfs limits the maximum filename length to 255. However, the DNS limits the maximum lookup length and, by extension, the maximum cell name, to 255 less two (length count and trailing NUL). Fix this by limiting the maximum acceptable cellname length to 253. This also allows us to be sure we can create the "/afs/.<cell>/" mountpoint too. Further, split the YFS VL record cell name maximum to be the 256 allowed by the protocol and ignore the record retrieved by YFSVL.GetCellName if it exceeds 253.. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: afs: Fix the maximum cell name length The kafs filesystem limits the maximum length of a cell to 256 bytes, but a problem occurs if someone actually does that: kafs tries to create a directory under /proc/net/afs/ with the name of the cell, but that fails with a warning: WARNING: CPU: 0 PID: 9 at fs/proc/generic.c:405 because procfs limits the maximum filename length to 255. However, the DNS limits the maximum lookup length and, by extension, the maximum cell name, to 255 less two (length count and trailing NUL). Fix this by limiting the maximum acceptable cellname length to 253. This also allows us to be sure we can create the "/afs/.<cell>/" mountpoint too. Further, split the YFS VL record cell name maximum to be the 256 allowed by the protocol and ignore the record retrieved by YFSVL.GetCellName if it exceeds 253.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.8, < 5.10.234 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.177 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.125 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.72 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.10 | — |
| Linux | Linux Kernel | 6.13 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-21646?
How severe is CVE-2025-21646?
How do I fix CVE-2025-21646?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-21640In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21641In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21642In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21643In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21644In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21645In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21647In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-21648In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-21649In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-2165The SH Email Alert plugin for WordPress is vulnerable to Ref…6.1
- CVE-2025-21650In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-21651In the Linux kernel, the following vulnerability has been re…4.7
Are you affected by CVE-2025-21646?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
