Re: [PATCH 0/2] authencesn: Refactor in-place decryption

[Scott Guo <scott_gzh@163.com>]

Then the problem comes down to whether ESP will be able to identify all 
the path and mitigate all of it.

I am also wondering whether this in-place crypto + SG list method would 
have simular issue with other crypto such as SKCipher. Copy Failed, 
Dirty Frag and Fragnesia is ultimately an attack that craft specific 
bytes with encryption and decryption. Attacker would potentially be able 
to archieve a collision attack on say the record for root in passwd file 
and use it on any machine where their passwd files are in a simular format.

在 2026/5/18 11:17, Herbert Xu 写道:
> On Mon, May 18, 2026 at 10:55:38AM +0800, Scott Guo wrote:
>> BTW, I am wondering whether we should disable inplace decryption for now? I
>> think that to mitigate vulnerabilities like Fragnesia, maybe something has
>> to be done on the memory side. Maybe something like forcing a pagefault when
>> trying to write to these pages?
> 
> I think stopping ESP from putting frags into the dst SG list would
> be prudent until the whole stack has been audited.
> 
> Alternatively switch from the black-list to a white-list approach
> and only allow ESP to do in-place processing of packets from a
> source that's known to be writable.
> 
> Cheers,