lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Wed, 09 Mar 2022 06:30:10 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Tung Nguyen <tung.q.nguyen@...tech.com.au>
Cc:     netdev@...r.kernel.org, tipc-discussion@...ts.sourceforge.net,
        davem@...emloft.net, kuba@...nel.org, ying.xue@...driver.com,
        jmaloy@...hat.com
Subject: Re: [PATCH net 1/1] tipc: fix incorrect order of state message data
 sanity check

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@...nel.org>:

On Tue,  8 Mar 2022 02:11:59 +0000 you wrote:
> When receiving a state message, function tipc_link_validate_msg()
> is called to validate its header portion. Then, its data portion
> is validated before it can be accessed correctly. However, current
> data sanity  check is done after the message header is accessed to
> update some link variables.
> 
> This commit fixes this issue by moving the data sanity check to
> the beginning of state message handling and right after the header
> sanity check.
> 
> [...]

Here is the summary with links:
  - [net,1/1] tipc: fix incorrect order of state message data sanity check
    https://git.kernel.org/netdev/net/c/c79fcc27be90

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ