From: David Timber <dxdt@dev.snart.me>
To: linkinjeon@kernel.org, sj1557.seo@samsung.com,
linux-fsdevel@vger.kernel.org
Cc: yuezhang.mo@sony.com, David Timber <dxdt@dev.snart.me>
Subject: [PATCH v0 0/1] exfat: set s_maxbytes
Date: Tue, 17 Mar 2026 06:41:36 +0900 [thread overview]
Message-ID: <20260316214137.1490070-1-dxdt@dev.snart.me> (raw)
Possible security impact when a file in an exFAT volume larger than
16TB(MAX_LFS_FILESIZE) is mmap()'d on 32-bit machines due to potential
undefined behaviour in filemap. Though the attack surface is quite
limited as mmap() is rarely used with exFAT. The comment on the macro
definition is pretty much self-explanatory.
The use of unsigned int became apparently evil ever since Linux
switched its own loff_t. Integer overflows could go undetected.
David Timber (1):
exfat: fix s_maxbytes
fs/exfat/exfat_raw.h | 1 +
fs/exfat/file.c | 1 +
fs/exfat/super.c | 11 ++++++++---
3 files changed, 10 insertions(+), 3 deletions(-)
--
2.53.0.1.ga224b40d3f.dirty
next reply other threads:[~2026-03-16 21:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 21:41 David Timber [this message]
2026-03-16 21:41 ` [PATCH v0 1/1] exfat: fix s_maxbytes David Timber
2026-03-19 12:38 ` Namjae Jeon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260316214137.1490070-1-dxdt@dev.snart.me \
--to=dxdt@dev.snart.me \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=yuezhang.mo@sony.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox