From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99725: cipso: fix optlen corruption in cipso_v4_delopt()
Date: Fri, 20 Nov 2026 06:51:51 +0100 [thread overview]
Message-ID: <2026112011-CVE-2026-99725-dbfb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
cipso: fix optlen corruption in cipso_v4_delopt()
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.
Compute the new length from the intact options before the move and
subtract the CIPSO length, and fill the padding with IPOPT_END.
The Linux kernel CVE team has assigned CVE-2026-99725 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.28 with commit 014ab19a69c325f52d7bae54ceeda73d6307ae0c and fixed in 6.12.118 with commit 699141380f7f249b7ee594198d9bea6bcd4862ea
Issue introduced in 2.6.28 with commit 014ab19a69c325f52d7bae54ceeda73d6307ae0c and fixed in 6.18.64 with commit 4077bd2bcebf43922f84aa87f6839153212df509
Issue introduced in 2.6.28 with commit 014ab19a69c325f52d7bae54ceeda73d6307ae0c and fixed in 7.3.5 with commit 0d9a6f9778ccd4401ded4ec9faf750b7b4a14ce7
Issue introduced in 2.6.28 with commit 014ab19a69c325f52d7bae54ceeda73d6307ae0c and fixed in 7.4-rc2 with commit 1f1f8e8c5176234fa31858cd25f2e9b88aac0a45
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-99725
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
net/ipv4/cipso_ipv4.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/699141380f7f249b7ee594198d9bea6bcd4862ea
https://git.kernel.org/stable/c/4077bd2bcebf43922f84aa87f6839153212df509
https://git.kernel.org/stable/c/0d9a6f9778ccd4401ded4ec9faf750b7b4a14ce7
https://git.kernel.org/stable/c/1f1f8e8c5176234fa31858cd25f2e9b88aac0a45
reply other threads:[~2026-11-20 5:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2026112011-CVE-2026-99725-dbfb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.