linux-kernel - [Bug] "general protection fault in calipso_sock

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-next>] [day] [month] [year] [list]

Message-ID: <CAP=Rh=M1LzunrcQB1fSGauMrJrhL6GGps5cPAKzHJXj6GQV+-g@mail.gmail.com>
Date: Wed, 21 May 2025 22:50:38 +0800
From: John <john.cs.hey@...il.com>
To: "David S. Miller" <davem@...emloft.net>, David Ahern <dsahern@...nel.org>, 
	Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>
Cc: Simon Horman <horms@...nel.org>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [Bug] "general protection fault in calipso_sock_setattr" in Linux
 kernel v6.12

Dear Linux Kernel Maintainers,

I hope this message finds you well.

I am writing to report a potential vulnerability I encountered during
testing of the Linux Kernel version v6.12.

Git Commit: adc218676eef25575469234709c2d87185ca223a (tag: v6.12)

Bug Location: calipso_sock_setattr+0xf6/0x380 net/ipv6/calipso.c:1128

Bug report: https://hastebin.com/share/iredodibar.yaml

Complete log: https://hastebin.com/share/biqowozonu.perl

Entire kernel config: https://hastebin.com/share/huqucavidu.ini

Root Cause Analysis:
The crash is caused by a NULL pointer dereference in txopt_get() (at
include/net/ipv6.h:390) due to an uninitialized struct inet6_opt *opt
field.
The function is indirectly invoked during an SELinux policy
enforcement path via calipso_sock_setattr(), which expects an
initialized inet6_sk(sk)->opt structure.
However, the socket in question does not have IPv6 tx options set up
at the time of the call, likely due to missing or out-of-order
initialization during socket creation or connection setup.
This leads to an invalid access at offset +0x70, detected by KASAN,
and results in a general protection fault.

At present, I have not yet obtained a minimal reproducer for this
issue. However, I am actively working on reproducing it, and I will
promptly share any additional findings or a working reproducer as soon
as it becomes available.

Thank you very much for your time and attention to this matter. I
truly appreciate the efforts of the Linux kernel community.

Best regards,
John