CopyFail 未向发行版披露
CopyFail was not disclosed to Gentoo developer

原始链接: https://www.openwall.com/lists/oss-security/2026/04/30/10

这封邮件讨论了CVE-2026-31431,一个Linux内核中的严重“CopyFail”漏洞,允许本地权限提升。该问题出现在4.14版本的内核中(提交72548b093ee38a6d4f2a19e6ef1948ae05c181f7),并在6.18.22、6.19.12和7.0版本中得到修复,包含特定提交。 然而,较旧的长期支持(LTS)内核 – 6.12、6.6、6.1、5.15和5.10 – 仍然未修复。由于API变更,将修复移植到这些旧版本变得困难。一个临时补丁正在共享,但承认它可能并不完美。 讨论强调了针对此内核漏洞,分发方缺乏提前预警,因为报告者没有使用linux-distros邮件列表。该漏洞被认为非常严重,促使快速响应和临时解决方案的开发。

Hacker News 新闻 | 过去 | 评论 | 提问 | 展示 | 工作 | 提交 登录 CopyFail 未向发行版披露 (openwall.com) 29 分,ori_b 1小时前 | 隐藏 | 过去 | 收藏 | 1 条评论 帮助 xeeeeeeeeeeenu 2分钟前 [–] 背景信息:链接文章的作者 Sam James 是 Gentoo 的开发者。总之,这是一场灾难。在发行版发布修复程序之前向世界分享漏洞是非常不负责任的。谁知道有多少共享主机提供商因此被攻击了。 同样令人担忧的是,内核安全团队和发行版维护者之间似乎缺乏沟通。人们希望前者会通知后者,但显然,发现漏洞的人有责任这样做。回复 考虑申请 YC 2026 年夏季批次!申请截止至 5 月 4 日 指南 | 常见问题 | 列表 | API | 安全 | 法律 | 申请 YC | 联系方式 搜索:
相关文章

原文
oss-security - Re: CVE-2026-31431: CopyFail: linux local privilege scalation [<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <[email protected]>
Date: Thu, 30 Apr 2026 05:52:37 +0100
From: Sam James <[email protected]>
To: [email protected]
Cc: Jan Schaumann <[email protected]>
Subject: Re: CVE-2026-31431: CopyFail: linux local privilege
 scalation

Eddie Chapman <[email protected]> writes:

> On 29/04/2026 21:23, Jan Schaumann wrote:
>> Affected and fixed versions
>> ===========================
>> Issue introduced in 4.14 with commit
>> 72548b093ee38a6d4f2a19e6ef1948ae05c181f7 and fixed in
>> 6.18.22 with commit
>> fafe0fa2995a0f7073c1c358d7d3145bcc9aedd8
>> Issue introduced in 4.14 with commit
>> 72548b093ee38a6d4f2a19e6ef1948ae05c181f7 and fixed in
>> 6.19.12 with commit
>> ce42ee423e58dffa5ec03524054c9d8bfd4f6237
>> Issue introduced in 4.14 with commit
>> 72548b093ee38a6d4f2a19e6ef1948ae05c181f7 and fixed in
>> 7.0 with commit
>> a664bf3d603dc3bdcf9ae47cc21e0daec706d7a5
>> https://git.kernel.org/stable/c/fafe0fa2995a0f7073c1c358d7d3145bcc9aedd8
>> https://git.kernel.org/stable/c/ce42ee423e58dffa5ec03524054c9d8bfd4f6237
>> https://git.kernel.org/stable/c/a664bf3d603dc3bdcf9ae47cc21e0daec706d7a5
>
> So this is one of the worst make-me-root vulnerabilities in the kernel
> in recent times. I see that on the 11th of April 6.19.12 & 6.18.22
> were released with the fix backported.
>
> Longterm 6.12, 6.6, 6.1, 5.15, 5.10 have not received the fix and I
> don't see anything in the upstream stable queues yet as I write. My
> guess is backporting that far back is not as straightforward. As this
> was introduced in 2017 all those older kernels are affected, right? Or
> am I missing something?

It does not apply cleanly, no. Attached is the workaround we're going to
use. I'm not an expert on IPSec but I think this is the lesser evil.

I attempted a backport but ran into a few API changes and wasn't
confident enough to muck around with it, especially for something to
deploy immediately.

> [...]
>
> What went wrong, has the embargo been broken early today? Not looking
> to point any fingers, those who make things happen in our communities
> work dam hard and deserve respect and support, especially with the
> extra burden of AI slop now.

Note that for Linux kernel vulnerabilities, unless the reporter chooses
to bring it to the linux-distros ML, there is no heads-up to
distributions.

It did not happen here.

>
> Eddie

sam


View attachment "0001-crypto-disable-authencesn-module-for-CVE-2026-31431.patch" of type "text/x-patch" (1543 bytes)

Download attachment "signature.asc" of type "application/pgp-signature" (419 bytes)

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.

联系我们 contact @ memedata.com