Linux Security Modules development
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Qihang <q.h.hack.winter@gmail.com>
Cc: netdev@vger.kernel.org, paul@paul-moore.com,
	linux-security-module@vger.kernel.org, omniameasunt@proton.me
Subject: Re: [PATCH net v4] cipso: fix optlen corruption in cipso_v4_delopt()
Date: Mon, 02 Nov 2026 13:00:04 +0000	[thread overview]
Message-ID: <179362440455.4016458.9024394156701425815.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261029033942.3644-1-q.h.hack.winter@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Dave Miller <davem@davem-thinkpadp1gen8.ibmlond.csb>:

On Thu, 29 Oct 2026 11:39:42 +0800 you wrote:
> cipso_v4_delopt() recomputes the option length by walking the option
> buffer after the CIPSO option has been moved out.  The walk then reads
> the stale bytes at the tail of the buffer as option data, and a crafted
> setsockopt(IP_OPTIONS) buffer can make it treat one of them as an option
> length, increasing opt->opt.optlen beyond the valid option data.
> 
> The corrupted length stays on the socket and is later used as the copy
> length by getsockopt(IP_OPTIONS) and by the udp/raw/ping sendmsg paths,
> where it exceeds the size of the buffers they copy into.
> 
> [...]

Here is the summary with links:
  - [net,v4] cipso: fix optlen corruption in cipso_v4_delopt()
    https://git.kernel.org/netdev/net/c/1f1f8e8c5176

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



      parent reply	other threads:[~2026-11-02 13:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  3:39 [PATCH net v4] cipso: fix optlen corruption in cipso_v4_delopt() Qihang
2026-10-29  3:46 ` netdev-bot+sinfo
2026-10-29  3:53 ` sashiko-bot
2026-10-29 13:55 ` Paul Moore
     [not found]   ` <CAH78GvvgG0GpuR9bvM7fDDz-mpakfBuvC418-nEBUrA9pR8suw@mail.gmail.com>
2026-11-01 14:10     ` Qihang
2026-11-02 13:00 ` patchwork-bot+netdevbpf [this message]

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=179362440455.4016458.9024394156701425815.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=omniameasunt@proton.me \
    --cc=paul@paul-moore.com \
    --cc=q.h.hack.winter@gmail.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