nday
CVE-2025-40246

xfs: fix out of bounds memory read error in symlink repair

Linux / Linux

CVE 공개: . nday가 아직 패치 근거를 수집하지 않았습니다. 패치가 없다는 뜻은 아닙니다. PoC 출처 4곳 모두 미등재. CISA KEV 미등재.

tags productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

Linux kernel
affected products in the CVE record: Linux · Linux
operating system
affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
현재 단계
DIS
공개
CVSS
점수 없음

생명주기

가로축 UTC. 점 = 분 단위, 넓은 막대 = 날짜만, 빈 표시 = 불명 또는 추정.
시점 알 수 없음
DIS공개
2025-12-04T16:08Z
PAT패치
아직 기록 없음
ANA분석
아직 기록 없음
POCPoC
아직 기록 없음
ITW악용
아직 기록 없음
KEVKEV
아직 기록 없음

요약

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

xfs: fix out of bounds memory read error in symlink repair

xfs/286 produced this report on my test fleet:

==================================================================
BUG: KFENCE: out-of-bounds read in memcpy_orig+0x54/0x110

Out-of-bounds read at 0xffff88843fe9e038 (184B right of kfence-#184):
 memcpy_orig+0x54/0x110
 xrep_symlink_salvage_inline+0xb3/0xf0 [xfs]
 xrep_symlink_salvage+0x100/0x110 [xfs]
 xrep_symlink+0x2e/0x80 [xfs]
 xrep_attempt+0x61/0x1f0 [xfs]
 xfs_scrub_metadata+0x34f/0x5c0 [xfs]
 xfs_ioc_scrubv_metadata+0x387/0x560 [xfs]
 xfs_file_ioctl+0xe23/0x10e0 [xfs]
 __x64_sys_ioctl+0x76/0xc0
 do_syscall_64+0x4e/0x1e0
 entry_SYSCALL_64_after_hwframe+0x4b/0x53

kfence-#184: 0xffff88843fe9df80-0xffff88843fe9dfea, size=107, cache=kmalloc-128

allocated by task 3470 on cpu 1 at 263329.131592s (192823.508886s ago):

 xfs_init_local_fork+0x79/0xe0 [xfs]
 xfs_iformat_local+0xa4/0x170 [xfs]
 xfs_iformat_data_fork+0x148/0x180 [xfs]
 xfs_inode_from_disk+0x2cd/0x480 [xfs]
 xfs_iget+0x450/0xd60 [xfs]
 xfs_bulkstat_one_int+0x6b/0x510 [xfs]
 xfs_bulkstat_iwalk+0x1e/0x30 [xfs]
 xfs_iwalk_ag_recs+0xdf/0x150 [xfs]
 xfs_iwalk_run_callbacks+0xb9/0x190 [xfs]
 xfs_iwalk_ag+0x1dc/0x2f0 [xfs]
 xfs_iwalk_args.constprop.0+0x6a/0x120 [xfs]
 xfs_iwalk+0xa4/0xd0 [xfs]
 xfs_bulkstat+0xfa/0x170 [xfs]
 xfs_ioc_fsbulkstat.isra.0+0x13a/0x230 [xfs]
 xfs_file_ioctl+0xbf2/0x10e0 [xfs]
 __x64_sys_ioctl+0x76/0xc0
 do_syscall_64+0x4e/0x1e0
 entry_SYSCALL_64_after_hwframe+0x4b/0x53

CPU: 1 UID: 0 PID: 1300113 Comm: xfs_scrub Not tainted 6.18.0-rc4-djwx #rc4 PREEMPT(lazy)  3d744dd94e92690f00a04398d2bd8631dcef1954
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-4.module+el8.8.0+21164+ed375313 04/01/2014
==================================================================

On further analysis, I realized that the second parameter to min() is not correct. xfs_ifork::if_bytes is the size of the xfs_ifork::if_data buffer. if_bytes can be smaller than the data fork size because:

(a) the forkoff code tries to keep the data area as large as possible (b) for symbolic links, if_bytes is the ondisk file size + 1 (c) forkoff is always a multiple of 8.

Case in point: for a single-byte symlink target, forkoff will be 8 but the buffer will only be 2 bytes long.

In other words, the logic here is wrong and we walk off the end of the incore buffer. Fix that.

Original text of the CVE record (cvelist), shown as published.

이벤트 로그

+DISCVE 공개

CVE 레코드 공개(CNA: Linux).

출처 cvelist · nday 일괄 수집 · 원본
{
  "id": 375708,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2025-40246",
  "occurred_at": "2025-12-04T16:08:09.751Z",
  "observed_at": "2026-11-13T05:39:08.090137Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2025-12-04T16:08:09.751Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

연구자 논의

최근 7일간 연구자 0명이 언급

목록의 연구자가 X에서 이 CVE를 언급한 게시물입니다. 원문 그대로 보여 주며 nday는 검증하지 않습니다.

명단의 연구자가 X에서 이 CVE를 언급한 게시물은 아직 수집되지 않았습니다.

Discussion

0 comments

No comments yet.