PT-2026-151673
CVE-2026-99462
·
Publicado
2026-11-19
·
Atualizado
2026-11-19
Descrição por
Pontuação
N/A
Não disponívelNã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:
mm/truncate: look up the end-edge straddler by index
In truncate inode partial folio(), after the first split at the start
edge, folio split() unlocks and drops the refcount of the after-split
sub-folios. The sub-folio straddling the end of the truncation range is
therefore unlocked and only transiently ref'd in the page cache while the
code still derives it from a page pointer inside the original folio.
Between the first split finishing and page folio() resolving split at2,
that tail page can be reclaimed, freed and reallocated as a new large
folio in the same mapping at a different file offset. folio2 then points
at a folio that does not cover the end boundary, yet folio2->mapping ==
folio->mapping still holds, so the stale pointer passes the mapping check
and folio split or unmap() splits a folio at a wrong position (or, with a
transient refcount, a use-after-free window opens between try get and the
split). folio split()'s own folio != page folio(split at) check cannot
catch this either since split at2 has been reallocated as part of the new
folio, so page folio(split at2) resolves back to folio2.
Look the straddler up by its page index instead. filemap get folio()
returns the folio currently covering the boundary, ref'd and locked, with
the mapping validated under the lock, so the split target is always the
real folio at the end edge.
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾