PT-2026-152456

CVE-2026-99576

·

Publicado

2026-11-20

·

Atualizado

2026-11-20

Descrição por

Pontuação
N/A
Não disponível

Não há classificações de severidade ou métricas disponíveis. Quando houver, atualizaremos as informações correspondentes na página.

In the Linux kernel, the following vulnerability has been resolved:
f2fs: zone: fix to avoid bio split on sequential zone
In the block layer, bio split to limits() splits a bio if it exceeds any underlying queue limits:
  1. queue max sectors: Splits bios larger than the transfer limit. This limit is set by the device driver/DMA controller (max hw sectors) and device-mapper targets. When flushing dirty pages (governed by VFS writeback chunk size() and f2fs nr pages to skip()), f2fs merges contiguous pages into bios up to 512KB (1024 sectors) or more without checking queue max sectors, which will be split if the device or DM target enforces a smaller limit.
  2. queue max segments: Splits bios exceeding scatter-gather segment limits. f2fs allocates bios with up to 256 pages, exceeding the 128-segment limit of DM targets (dm-default-key/dm-crypt) if pages are discontiguous.
  3. chunk sectors: Splits bios crossing chunk/zone boundaries. In f2fs, section size strictly matches zone size, and block allocation never spans across section boundaries, so bios never cross chunk sectors.
Crucially, when bio split to limits() splits a bio, bio submit split() submits the tail half via submit bio noacct() before returning the head half to the caller. On a sequential zoned device, this causes the tail bio to arrive at the zone write plug before the head:
dm-3: zone 7: prepare bio wp mismatch: bio sector 30720 offset 2048 != wp offset 248, len 248
The write plug rejects the out-of-order tail with BLK STS IOERR, causing f2fs stop checkpoint() and remounting the filesystem read-only:
2026-09-30T22:09:23.725678+08:00 localhost kernel: CPU: 9 UID: 0 PID: 243 Comm: kworker/9:1H Not tainted 6.12.81-gb3ef518fb26d #5 2026-09-30T22:09:23.725750+08:00 localhost kernel: Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.17.0-debian-1.17.0-1 04/01/2014 2026-09-30T22:09:23.725753+08:00 localhost kernel: Workqueue: dm-3 zwplugs blk zone wplug bio work 2026-09-30T22:09:23.725756+08:00 localhost kernel: Call Trace: 2026-09-30T22:09:23.725758+08:00 localhost kernel: 2026-09-30T22:09:23.725758+08:00 localhost kernel: dump stack lvl+0x4d/0x70 2026-09-30T22:09:23.725759+08:00 localhost kernel: f2fs stop checkpoint+0x1df/0x5d0 2026-09-30T22:09:23.725759+08:00 localhost kernel: ? blk zone wplug bio work+0x4eb/0x740 2026-09-30T22:09:23.725760+08:00 localhost kernel: f2fs cache write end io+0x545/0x6e0 2026-09-30T22:09:23.725761+08:00 localhost kernel: blk zone wplug bio work+0x4eb/0x740 2026-09-30T22:09:23.725762+08:00 localhost kernel: process one work+0x5c6/0xde0 2026-09-30T22:09:23.725764+08:00 localhost kernel: ? assign work+0x124/0x4e0 2026-09-30T22:09:23.725765+08:00 localhost kernel: worker thread+0x403/0xb70 2026-09-30T22:09:23.725765+08:00 localhost kernel: ? kthread parkme+0x82/0x140 2026-09-30T22:09:23.725766+08:00 localhost kernel: ? pfx worker thread+0x10/0x10 2026-09-30T22:09:23.725766+08:00 localhost kernel: kthread+0x235/0x2e0 2026-09-30T22:09:23.725767+08:00 localhost kernel: ? recalc sigpending+0x128/0x1d0 2026-09-30T22:09:23.725767+08:00 localhost kernel: ? pfx kthread+0x10/0x10 2026-09-30T22:09:23.725769+08:00 localhost kernel: ret from fork+0x2f/0x70 2026-09-30T22:09:23.725769+08:00 localhost kernel: ? pfx kthread+0x10/0x10 2026-09-30T22:09:23.725770+08:00 localhost kernel: ret from fork asm+0x1a/0x30 2026-09-30T22:09:23.725771+08:00 localhost kernel: 2026-09-30T22:09:23.725771+08:00 localhost kernel: F2FS-fs (dm-0): Stopped filesystem due to reason: 3
To prevent write bios destined for sequential zones from being split:
  1. In bio alloc(), bound npages to bdev max segments(bdev) for writes to sequential zone areas.
  2. In page is mergeable(), check queue max segments() and queue max sectors() for sequential zone areas, so f2fs will not merge beyond the queue limits.
Fornecedores
Produtos afetados
Identificadores relacionados
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾