Star12
93
代码
代码
Issues5517
Pull Requests8
项目讨论
Wiki
分析
Star12
93
已开启
CVE-2026-63942 #16269
openeuler-ci-bot创建于  7月20日
openeuler-ci-bot
openeuler-ci-bot成员
7月20日 创建

一、漏洞信息
漏洞编号：CVE-2026-63942
漏洞归属组件：kernel
漏洞归属的版本：4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.12.33,6.18.18,6.4.0,6.6.0
CVSS评分：
BaseScore：7.8 High
Vector：CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
漏洞简述：
In the Linux kernel, the following vulnerability has been resolved:parport: Fix race between port and client registrationThe parport subsystem registers port devices before they are fullyinitialised, resulting in a race condition where client drivers suchas lp can attach to ports that are not completely initialised or evenbeing torn down.When the port and client drivers are built as modules and loadedaround the same time during boot, this occasionally results in acrash. I was able to make this happen reliably in a VM with aPC-style parallel port by patching parport_pc to fail probing:> --- a/drivers/parport/parport_pc.c> +++ b/drivers/parport/parport_pc.c> @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,> if (!p)> goto out3;>> - base_res = request_region(base, 3, p->name);> + base_res = NULL;> if (!base_res)> goto out4;>and then running: while true; do modprobe lp & modprobe parport_pc wait rmmod lp parport_pc donefor a few seconds.In the long term I think port registration should be changed to putthe call to device_add() inside parport_announce_port(), but since thelatter currently cannot fail this will require changing all portdrivers.For now, add a flag to indicate whether a port has been announced and only try to attach client drivers to ports when the flag is set.
漏洞公开时间：2026-07-20 00:17:12
漏洞创建时间：2026-07-20 10:16:41
漏洞详情参考链接：
https://nvd.nist.gov/vuln/detail/CVE-2026-63942

更多参考(点击展开)
参考来源 参考链接 来源链接
https://git.kernel.org/stable/c/f3378b0d7bd4605de89b083b2900788157a181cc
https://git.kernel.org/stable/c/d16548be2ea5058227d79799e81dab61c9bca8ec
https://www.cve.org/CVERecord?id=CVE-2026-63942
https://git.kernel.org/stable/c/290f515c5e3b3900bc2fe24f179999fd08d23bfa
https://lore.kernel.org/linux-cve-announce/2026071953-CVE-2026-63942-2771@gregkh/T
https://git.kernel.org/stable/c/a1e81b58da0179531bedf0b9f2811f5f992d5c4b
https://git.kernel.org/stable/c/ef15ccbb3e8640a723c42ad90eaf81d66ae02017
https://bugzilla.redhat.com/show_bug.cgi?id=2502323
https://git.kernel.org/stable/c/74d6aae1df45d3414178986be743f946988fddf6
https://nvd.nist.gov/vuln/detail/CVE-2026-63942
https://git.kernel.org/stable/c/51026cff1f4f3b762a0b5a07c727bd59cef45320
https://git.kernel.org/stable/c/15b1723c1472e802f9f7e69ae4e64f7dbf588848

漏洞分析指导链接：
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
七彩瞬析开源风险感知平台
漏洞补丁信息：

详情(点击展开)
影响的包 修复版本 修复补丁 问题引入补丁 来源
gregkh/linux https://git.kernel.org/stable/c/f3378b0d7bd4605de89b083b2900788157a181cc ljqc
gregkh/linux https://git.kernel.org/stable/c/290f515c5e3b3900bc2fe24f179999fd08d23bfa ljqc
gregkh/linux https://git.kernel.org/stable/c/d16548be2ea5058227d79799e81dab61c9bca8ec ljqc
gregkh/linux https://git.kernel.org/stable/c/15b1723c1472e802f9f7e69ae4e64f7dbf588848 ljqc
gregkh/linux https://git.kernel.org/stable/c/51026cff1f4f3b762a0b5a07c727bd59cef45320 ljqc
gregkh/linux https://git.kernel.org/stable/c/74d6aae1df45d3414178986be743f946988fddf6 ljqc
gregkh/linux https://git.kernel.org/stable/c/a1e81b58da0179531bedf0b9f2811f5f992d5c4b ljqc
gregkh/linux https://git.kernel.org/stable/c/ef15ccbb3e8640a723c42ad90eaf81d66ae02017 ljqc
https://git.kernel.org/stable/c/f3378b0d7bd4605de89b083b2900788157a181cc cvelistv5
https://git.kernel.org/stable/c/d16548be2ea5058227d79799e81dab61c9bca8ec cvelistv5
https://git.kernel.org/stable/c/290f515c5e3b3900bc2fe24f179999fd08d23bfa cvelistv5
https://git.kernel.org/stable/c/a1e81b58da0179531bedf0b9f2811f5f992d5c4b cvelistv5
https://git.kernel.org/stable/c/ef15ccbb3e8640a723c42ad90eaf81d66ae02017 cvelistv5
https://git.kernel.org/stable/c/74d6aae1df45d3414178986be743f946988fddf6 cvelistv5
https://git.kernel.org/stable/c/51026cff1f4f3b762a0b5a07c727bd59cef45320 cvelistv5
https://git.kernel.org/stable/c/15b1723c1472e802f9f7e69ae4e64f7dbf588848 cvelistv5

二、漏洞分析结构反馈
影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:parport: Fix race between port and client registrationThe parport subsystem registers port devices before they are fullyinitialised, resulting in a race condition where client drivers suchas lp can attach to ports that are not completely initialised or evenbeing torn down.When the port and client drivers are built as modules and loadedaround the same time during boot, this occasionally results in acrash. I was able to make this happen reliably in a VM with aPC-style parallel port by patching parport_pc to fail probing:<spanclass= q >> --- a/drivers/parport/parport_pc.c> +++ b/drivers/parport/parport_pc.c> @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,> if (!p)> goto out3;>> -base_res = request_region(base, 3, p->name);> +base_res = NULL;> if (!base_res)> goto out4;>and then running: while true; do modprobe lp & modprobe parport_pcwaitrmmod lp parport_pc donefor a few seconds.In the long term I think port registration should be changed to putthe call to device_add() inside parport_announce_port(), but since thelatter currently cannot fail this will require changing all portdrivers.For now, add a flag to indicate whether a port has been "announced"and only try to attach client drivers to ports when the flag is set.The Linux kernel CVE team has assigned CVE-2026-63942 to this issue.
openEuler评分：
7.8
Vector：CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
受影响版本排查(受影响/不受影响)：
1.master(6.18.40):不受影响
2.openEuler-20.03-LTS-SP4(4.19.90):受影响
3.openEuler-22.03-LTS-SP4(5.10.0):受影响
4.openEuler-24.03-LTS-Next(6.6.0):不受影响
5.openEuler-24.03-LTS-SP1(6.6.0):受影响
6.openEuler-24.03-LTS-SP3(6.6.0):受影响
7.openEuler-24.03-LTS-SP4(6.6.0):受影响
8.openEuler-22.03-LTS-SP3(5.10.0):受影响
9.openEuler-24.03-LTS(6.6.0):受影响
10.openEuler-24.03-LTS-SP2(6.6.0):受影响

修复是否涉及abi变化(是/否)：
1.master(6.18.40):否
2.openEuler-20.03-LTS-SP4(4.19.90):否
3.openEuler-22.03-LTS-SP4(5.10.0):否
4.openEuler-24.03-LTS-Next(6.6.0):否
5.openEuler-24.03-LTS-SP1(6.6.0):否
6.openEuler-24.03-LTS-SP3(6.6.0):否
7.openEuler-24.03-LTS-SP4(6.6.0):否
8.openEuler-22.03-LTS-SP3(5.10.0):否
9.openEuler-24.03-LTS(6.6.0):否
10.openEuler-24.03-LTS-SP2(6.6.0):否

原因说明：
1.master(6.18.40):不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4(4.19.90):暂不修复-暂无解决方案或补丁
3.openEuler-22.03-LTS-SP4(5.10.0):正常修复
4.openEuler-24.03-LTS-Next(6.6.0):不受影响-漏洞代码不能被攻击者触发
5.openEuler-24.03-LTS-SP1(6.6.0):正常修复
6.openEuler-24.03-LTS-SP3(6.6.0):正常修复
7.openEuler-24.03-LTS-SP4(6.6.0):正常修复
8.openEuler-22.03-LTS-SP3(5.10.0):不修复-超出修复范围
9.openEuler-24.03-LTS(6.6.0):不修复-超出修复范围
10.openEuler-24.03-LTS-SP2(6.6.0):不修复-超出修复范围

likedislike
openeuler-ci-botopeneuler-ci-bot成员
7月20日 添加了label：CVE/UNFIXED
openeuler-ci-bot
openeuler-ci-bot成员
7月20日 评论：

issue处理注意事项:
1. 提交正常修复分支的修复PR时,必须关联当前issue,否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复;
注: 内容的关键词(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.

影响性分析说明:

openEuler评分: (评分和向量)

受影响版本排查(受影响/不受影响):
1.master(6.18.18):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP4(5.10.0):
4.openEuler-24.03-LTS-Next(6.6.0):
5.openEuler-24.03-LTS-SP1(6.6.0):
6.openEuler-24.03-LTS-SP3(6.6.0):
7.openEuler-24.03-LTS-SP4(6.6.0):

修复是否涉及abi变化(是/否)：
1.master(6.18.18):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP4(5.10.0):
4.openEuler-24.03-LTS-Next(6.6.0):
5.openEuler-24.03-LTS-SP1(6.6.0):
6.openEuler-24.03-LTS-SP3(6.6.0):
7.openEuler-24.03-LTS-SP4(6.6.0):

原因说明：
1.master(6.18.18):
2.openEuler-20.03-LTS-SP4(4.19.90):
3.openEuler-22.03-LTS-SP4(5.10.0):
4.openEuler-24.03-LTS-Next(6.6.0):
5.openEuler-24.03-LTS-SP1(6.6.0):
6.openEuler-24.03-LTS-SP3(6.6.0):
7.openEuler-24.03-LTS-SP4(6.6.0):

原因说明填写请参考下方表格(注意：版本是否受影响和版本的原因说明必须对应，例如master版本分支受影响，那原因说明只能是受影响对应的原因之一!)：

分支状态
原因说明 使用场景
受影响 正常修复 受影响且需要修复（包含升级版本修复）的漏洞；
受影响且已经修复的漏洞（历史修复PR也需要关联issue）；
若因特殊原因无法修复，应修改原因说明为【不修复-特殊原因】，并在安委会备案相关情况。
受影响 漏洞仍在分析中 已关注到相关漏洞，正在处理，未明确漏洞影响和修复方案。
受影响 暂不修复-暂无解决方案或补丁 当前没有可用的修复或补救措施。【影响性分析】中应包含有关为什么没有修复或补救措施的详细说明、上游相关PR等。
受影响 不修复-超出修复范围 没有漏洞的修复计划。当版本停维、软件包宣布生命周期终止或弃用使用。
受影响 不修复-特殊原因导致不再修复 如存在其他特殊情况不修复相关漏洞，或评估后无法升级修复，应在openEuler社区安全委员会例会进行说明备案。
【影响性分析】中应包含不发布修复的详细说明、特殊情况还应有安委会会议纪要。
不受影响 不受影响-组件不存在 软件不受影响，因为易受攻击的组件不在产品中。
不受影响 不受影响-已有内置的内联控制或缓解措施 内置的内联控制或缓解措施可防止攻击者利用漏洞
不受影响 不受影响-漏洞代码不能被攻击者触发 易受攻击的组件存在，并且该组件包含易受攻击的代码。但是，易受攻击的代码的使用方式使得攻击者无法进行任何预期的攻击。
不受影响 不受影响-漏洞代码不在执行路径 易受影响的代码在执行过程中不可访问，包括产品的非预期状态。产品不使用也不执行的组件。
不受影响 不受影响-漏洞代码不存在 产品不受影响，因为漏洞背后的代码在产品中不存在。与component_not_present不同的是，有问题的组件存在，但由于某种原因（例如安全的编译器选项）使漏洞的特定代码不存在于组件中。

issue处理具体操作请参考:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://docs.atomgit.com/docs/help/home/org_project/pullrequests/pr-related-issue

likedislike
devstation-robot
devstation-robot
7月20日 评论：

检测到新建 CVE Issue，CVE-ID: CVE-2026-63942。

你可以通过以下两种方式使用 CVE 修复服务：

  1. 分支影响分析

    • 在本 Issue 下评论：/analysis_branches
    • 系统将自动分析各个分支是否受影响，并在本 Issue 下给出表格形式的分析结果；

  2. 在指定分支上创建 PR（修复提交）

    • 在本 Issue 下按如下格式评论（字段均为必填，每个字段单独一行）：
/create_pr

branch: OLK-6.6 OLK-5.10
name: dev
email: dev@devstation.com
  • 说明：
    • branch: 需要创建 PR 的目标分支列表，例如 OLK-6.6 OLK-5.10；
    • name: PR 签名人姓名（如责任人或安全负责人）；
    • email: PR 签名人邮箱；

系统会根据上述信息自动在指定分支上创建 PR，并在本 Issue 下反馈结果。

provided by DevStation.

likedislike
openeuler-ci-botopeneuler-ci-bot成员
7月20日 添加了label：sig/Kernel
openeuler-ci-bot
openeuler-ci-bot成员
7月20日 评论：

Welcome To openEuler Community

Hey @openeuler-ci-bot , thanks for your contribution to the community.

Bot Usage Manual

I'm the Bot here serving you. You can find the instructions on how to interact with me at Here . That means you can comment below every pull request or issue to trigger Bot Commands.

Contact Guide

If you have any questions, please contact the SIG: Kernel ,
and any of the maintainers: @hanjunguo, @oekernel, @sanglipeng, @wkfxxx, @zeng_zhaorong ,
and any of the committers: @CTC-XiboWang, @Frank_Sae, @GoGo_phytium, @GongLei-, @LiuYongQiang0816, @SuperSix173, @Tankll2021, @TrueAI, @allen-shi, @baratta, @bibo_mao, @caixu-blue, @chen-jun-hw, @chenjiesong, @chenjunxin1992, @chenke2026, @chiqijun, @chriszjh, @duanqiangwen, @eingesch, @fangfeng123, @fanghaiqinghw, @gaojuxin09, @gouhao2022, @guohaocs2c, @guzitao, @hanjunguo, @hanliyang, @hellotcc, @henryze, @hewanhan, @hjx_gitff, @hongbo-lee, @hongwu-wang, @htforge, @hu-chunzhi, @hunan4222, @jackknight, @jerry_lilijun, @jiayi0118, @junlong-zheng, @juntianlinux, @kailiu42, @kaitiandu, @kazero00, @kevinzhu1, @kile2009, @koishimind, @kongzizaixian, @kylin-mayukun, @leoliu-oc, @li-huisong, @linan888, @linyunsheng, @liulongfang, @liyihang0226, @lostway1, @lujialin2, @mao-hongbo, @markyuan4ta21, @mawupeng, @mingqian218472, @mingrui-liu, @mufengyan, @pigalsofine, @robinorg, @rock_hw, @sanglipeng, @shu-shengming, @shuaijiakun, @sming56_admin, @stavewu, @stkid, @sun_nanyong, @wangboe2022, @wanghang73, @wenzhiwei11, @whoisxxx, @wkfxxx, @woqidaideshi, @wsoydl, @xingmz1, @xukuohai, @yeweihua999, @ygn-ndwd-official, @yonghu_4dc5, @young-sun, @yubo-liu1, @yuehaibing_planb, @yuzenghui1, @zhang-changzhong, @zhangyi089, @zhujianwei001, @zichengqu, @zouyipeng, @zqiao216 .

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
7月20日 评论：
参考网址 关联pr 状态 补丁链接
https://www.opencve.io/cve/CVE-2026-63942NoneNonehttps://git.kernel.org/stable/c/290f515c5e3b3900bc2fe24f179999fd08d23bfa
https://git.kernel.org/stable/c/ef15ccbb3e8640a723c42ad90eaf81d66ae02017
https://git.kernel.org/stable/c/f3378b0d7bd4605de89b083b2900788157a181cc
https://git.kernel.org/stable/c/15b1723c1472e802f9f7e69ae4e64f7dbf588848
https://git.kernel.org/stable/c/51026cff1f4f3b762a0b5a07c727bd59cef45320
https://git.kernel.org/stable/c/74d6aae1df45d3414178986be743f946988fddf6
https://git.kernel.org/stable/c/a1e81b58da0179531bedf0b9f2811f5f992d5c4b
https://git.kernel.org/stable/c/d16548be2ea5058227d79799e81dab61c9bca8ec
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2026-63942
https://security-tracker.debian.org/tracker/CVE-2026-63942NoneNonehttps://git.kernel.org/linus/ef15ccbb3e8640a723c42ad90eaf81d66ae02017
http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2026-63942
https://nvd.nist.gov/vuln/detail/CVE-2026-63942NoneNonehttps://git.kernel.org/stable/c/290f515c5e3b3900bc2fe24f179999fd08d23bfa
https://git.kernel.org/stable/c/ef15ccbb3e8640a723c42ad90eaf81d66ae02017
https://git.kernel.org/stable/c/f3378b0d7bd4605de89b083b2900788157a181cc
https://git.kernel.org/stable/c/15b1723c1472e802f9f7e69ae4e64f7dbf588848
https://git.kernel.org/stable/c/51026cff1f4f3b762a0b5a07c727bd59cef45320
https://git.kernel.org/stable/c/74d6aae1df45d3414178986be743f946988fddf6
https://git.kernel.org/stable/c/a1e81b58da0179531bedf0b9f2811f5f992d5c4b
https://git.kernel.org/stable/c/d16548be2ea5058227d79799e81dab61c9bca8ec
https://ubuntu.com/security/CVE-2026-63942

说明：补丁链接仅供初步排查参考，实际可用性请人工再次确认，补丁下载验证可使用CVE补丁工具。
若补丁不准确，烦请在此issue下评论 '/report-patch 参考网址 补丁链接1,补丁链接2' 反馈正确信息，便于我们不断优化工具，不胜感激。
如 /report-patch https://security-tracker.debian.org/tracker/CVE-2021-3997 https://github.com/systemd/systemd/commit/5b1cf7a9be37e20133c0208005274ce4a5b5c6a1

likedislike
openeuler-ci-botopeneuler-ci-bot成员
7月20日 修改了issue 的描述
H
hulk-ci-bot成员
7月20日 评论：

CVE-2026-63942

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

parport: Fix race between port and client registration

The parport subsystem registers port devices before they are fully
initialised, resulting in a race condition where client drivers such
as lp can attach to ports that are not completely initialised or even
being torn down.

When the port and client drivers are built as modules and loaded
around the same time during boot, this occasionally results in a
crash. I was able to make this happen reliably in a VM with a
PC-style parallel port by patching parport_pc to fail probing:

> --- a/drivers/parport/parport_pc.c
> +++ b/drivers/parport/parport_pc.c
> @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,
> if (!p)
> goto out3;
>
> - base_res = request_region(base, 3, p->name);
> + base_res = NULL;
> if (!base_res)
> goto out4;
>

and then running:

while true; do
    modprobe lp &#38; modprobe parport_pc
wait
rmmod lp parport_pc
done

for a few seconds.

In the long term I think port registration should be changed to put
the call to device_add() inside parport_announce_port(), but since the
latter currently cannot fail this will require changing all port
drivers.

For now, add a flag to indicate whether a port has been "announced"
and only try to attach client drivers to ports when the flag is set.

The Linux kernel CVE team has assigned CVE-2026-63942 to this issue.

openEuler评分:(评分和向量)
3.9
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L

受影响版本排查(受影响/不受影响):
1.master:不受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:受影响
5.openEuler-24.03-LTS:受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:受影响
8.openEuler-24.03-LTS-SP2:受影响
9.openEuler-24.03-LTS-SP3:受影响
10.openEuler-24.03-LTS-SP4:受影响

修复是否涉及abi变化(是/否)：
1.master:否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS-SP3:否
4.openEuler-22.03-LTS-SP4:否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-24.03-LTS-SP1:否
8.openEuler-24.03-LTS-SP2:否
9.openEuler-24.03-LTS-SP3:否
10.openEuler-24.03-LTS-SP4:否

原因说明：
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:暂不修复-漏洞仍在分析中
3.openEuler-22.03-LTS-SP3:不修复-超出修复范围
4.openEuler-22.03-LTS-SP4:暂不修复-漏洞仍在分析中
5.openEuler-24.03-LTS:不修复-超出修复范围
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:暂不修复-漏洞仍在分析中
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:暂不修复-漏洞仍在分析中
10.openEuler-24.03-LTS-SP4:暂不修复-漏洞仍在分析中

likedislike
openeuler-ci-botopeneuler-ci-bot成员
7月20日 修改了issue 的描述
openeuler-ci-bot
openeuler-ci-bot成员
7月20日 评论：

@GongLei- 经过 cve-manager 解析, 已分析的内容如下表所示:

状态 分析项目 内容
已分析 1.影响性分析说明 In the Linux kernel, the following vulnerability has been resolved:parport: Fix race between port and client registrationThe parport subsystem registers port devices before they are fullyinitialised, resulting in a race condition where client drivers suchas lp can attach to ports that are not completely initialised or evenbeing torn down.When the port and client drivers are built as modules and loadedaround the same time during boot, this occasionally results in acrash. I was able to make this happen reliably in a VM with aPC-style parallel port by patching parport_pc to fail probing:<spanclass="q">> --- a/drivers/parport/parport_pc.c> +++ b/drivers/parport/parport_pc.c> @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,> if (!p)> goto out3;>> -base_res = request_region(base, 3, p->name);> +base_res = NULL;> if (!base_res)> goto out4;>and then running: while true; do modprobe lp & modprobe parport_pcwaitrmmod lp parport_pc donefor a few seconds.In the long term I think port registration should be changed to putthe call to device_add() inside parport_announce_port(), but since thelatter currently cannot fail this will require changing all portdrivers.For now, add a flag to indicate whether a port has been "announced"and only try to attach client drivers to ports when the flag is set.The Linux kernel CVE team has assigned CVE-2026-63942 to this issue.
已分析 2.openEulerScore 3.9
已分析 3.openEulerVector AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L
已分析 4.受影响版本排查 master:不受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP3:受影响,openEuler-24.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-SP2:受影响
已分析 5.是否涉及abi变化 master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP3:否,openEuler-24.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-SP2:否
已分析 6.原因说明 master:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:漏洞仍在分析中,openEuler-22.03-LTS-SP4:漏洞仍在分析中,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-SP1:漏洞仍在分析中,openEuler-24.03-LTS-SP3:漏洞仍在分析中,openEuler-24.03-LTS-SP4:漏洞仍在分析中,openEuler-22.03-LTS-SP3:不修复-超出修复范围,openEuler-24.03-LTS:不修复-超出修复范围,openEuler-24.03-LTS-SP2:不修复-超出修复范围

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

likedislike
openeuler-ci-botopeneuler-ci-bot成员
7月20日 issue状态由 待办的 改变为 进行中
openeuler-ci-botopeneuler-ci-bot成员
7月21日 修改了issue 的描述
openeuler-ci-botopeneuler-ci-bot成员
7月24日 修改了issue 的描述
openeuler-ci-botopeneuler-ci-bot成员
7月25日 修改了issue 的描述
H
hulk-ci-bot成员
8月1日 评论：

CVE-2026-63942

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

parport: Fix race between port and client registration

The parport subsystem registers port devices before they are fully
initialised, resulting in a race condition where client drivers such
as lp can attach to ports that are not completely initialised or even
being torn down.

When the port and client drivers are built as modules and loaded
around the same time during boot, this occasionally results in a
crash. I was able to make this happen reliably in a VM with a
PC-style parallel port by patching parport_pc to fail probing:

> --- a/drivers/parport/parport_pc.c
> +++ b/drivers/parport/parport_pc.c
> @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,
> if (!p)
> goto out3;
>
> - base_res = request_region(base, 3, p->name);
> + base_res = NULL;
> if (!base_res)
> goto out4;
>

and then running:

while true; do
    modprobe lp &#38; modprobe parport_pc
wait
rmmod lp parport_pc
done

for a few seconds.

In the long term I think port registration should be changed to put
the call to device_add() inside parport_announce_port(), but since the
latter currently cannot fail this will require changing all port
drivers.

For now, add a flag to indicate whether a port has been "announced"
and only try to attach client drivers to ports when the flag is set.

The Linux kernel CVE team has assigned CVE-2026-63942 to this issue.

openEuler评分:(评分和向量)
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

受影响版本排查(受影响/不受影响):
1.master:不受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:受影响
5.openEuler-24.03-LTS:受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:受影响
8.openEuler-24.03-LTS-SP2:受影响
9.openEuler-24.03-LTS-SP3:受影响
10.openEuler-24.03-LTS-SP4:受影响

修复是否涉及abi变化(是/否)：
1.master:否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS-SP3:否
4.openEuler-22.03-LTS-SP4:否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-24.03-LTS-SP1:否
8.openEuler-24.03-LTS-SP2:否
9.openEuler-24.03-LTS-SP3:否
10.openEuler-24.03-LTS-SP4:否

原因说明：
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:不修复-超出修复范围
3.openEuler-22.03-LTS-SP3:不修复-超出修复范围
4.openEuler-22.03-LTS-SP4:暂不修复-漏洞仍在分析中
5.openEuler-24.03-LTS:不修复-超出修复范围
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:暂不修复-漏洞仍在分析中
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:暂不修复-漏洞仍在分析中
10.openEuler-24.03-LTS-SP4:暂不修复-漏洞仍在分析中

likedislike
openeuler-ci-botopeneuler-ci-bot成员
8月1日 修改了issue 的描述
openeuler-ci-bot
openeuler-ci-bot成员
8月1日 评论：

@GongLei- 经过 cve-manager 解析, 已分析的内容如下表所示:

状态 分析项目 内容
已分析 1.影响性分析说明 In the Linux kernel, the following vulnerability has been resolved:parport: Fix race between port and client registrationThe parport subsystem registers port devices before they are fullyinitialised, resulting in a race condition where client drivers suchas lp can attach to ports that are not completely initialised or evenbeing torn down.When the port and client drivers are built as modules and loadedaround the same time during boot, this occasionally results in acrash. I was able to make this happen reliably in a VM with aPC-style parallel port by patching parport_pc to fail probing:<spanclass="q">> --- a/drivers/parport/parport_pc.c> +++ b/drivers/parport/parport_pc.c> @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,> if (!p)> goto out3;>> -base_res = request_region(base, 3, p->name);> +base_res = NULL;> if (!base_res)> goto out4;>and then running: while true; do modprobe lp & modprobe parport_pcwaitrmmod lp parport_pc donefor a few seconds.In the long term I think port registration should be changed to putthe call to device_add() inside parport_announce_port(), but since thelatter currently cannot fail this will require changing all portdrivers.For now, add a flag to indicate whether a port has been "announced"and only try to attach client drivers to ports when the flag is set.The Linux kernel CVE team has assigned CVE-2026-63942 to this issue.
已分析 2.openEulerScore 7.8
已分析 3.openEulerVector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
已分析 4.受影响版本排查 master:不受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP3:受影响,openEuler-24.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-SP2:受影响
已分析 5.是否涉及abi变化 master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP3:否,openEuler-24.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-SP2:否
已分析 6.原因说明 master:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:不修复-超出修复范围,openEuler-22.03-LTS-SP4:漏洞仍在分析中,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-SP1:漏洞仍在分析中,openEuler-24.03-LTS-SP3:漏洞仍在分析中,openEuler-24.03-LTS-SP4:漏洞仍在分析中,openEuler-22.03-LTS-SP3:不修复-超出修复范围,openEuler-24.03-LTS:不修复-超出修复范围,openEuler-24.03-LTS-SP2:不修复-超出修复范围

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

likedislike
H
hulk-ci-bot成员
8月1日 评论：

CVE-2026-63942

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

parport: Fix race between port and client registration

The parport subsystem registers port devices before they are fully
initialised, resulting in a race condition where client drivers such
as lp can attach to ports that are not completely initialised or even
being torn down.

When the port and client drivers are built as modules and loaded
around the same time during boot, this occasionally results in a
crash. I was able to make this happen reliably in a VM with a
PC-style parallel port by patching parport_pc to fail probing:

> --- a/drivers/parport/parport_pc.c
> +++ b/drivers/parport/parport_pc.c
> @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,
> if (!p)
> goto out3;
>
> - base_res = request_region(base, 3, p->name);
> + base_res = NULL;
> if (!base_res)
> goto out4;
>

and then running:

while true; do
    modprobe lp &#38; modprobe parport_pc
wait
rmmod lp parport_pc
done

for a few seconds.

In the long term I think port registration should be changed to put
the call to device_add() inside parport_announce_port(), but since the
latter currently cannot fail this will require changing all port
drivers.

For now, add a flag to indicate whether a port has been "announced"
and only try to attach client drivers to ports when the flag is set.

The Linux kernel CVE team has assigned CVE-2026-63942 to this issue.

openEuler评分:(评分和向量)
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

受影响版本排查(受影响/不受影响):
1.master:不受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:受影响
5.openEuler-24.03-LTS:受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:受影响
8.openEuler-24.03-LTS-SP2:受影响
9.openEuler-24.03-LTS-SP3:受影响
10.openEuler-24.03-LTS-SP4:受影响

修复是否涉及abi变化(是/否)：
1.master:否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS-SP3:否
4.openEuler-22.03-LTS-SP4:否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-24.03-LTS-SP1:否
8.openEuler-24.03-LTS-SP2:否
9.openEuler-24.03-LTS-SP3:否
10.openEuler-24.03-LTS-SP4:否

原因说明：
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:不修复-超出修复范围
3.openEuler-22.03-LTS-SP3:不修复-超出修复范围
4.openEuler-22.03-LTS-SP4:暂不修复-漏洞仍在分析中
5.openEuler-24.03-LTS:不修复-超出修复范围
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:暂不修复-漏洞仍在分析中
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:暂不修复-漏洞仍在分析中
10.openEuler-24.03-LTS-SP4:暂不修复-漏洞仍在分析中

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
8月1日 评论：

@GongLei- 经过 cve-manager 解析, 已分析的内容如下表所示:

状态 分析项目 内容
已分析 1.影响性分析说明 In the Linux kernel, the following vulnerability has been resolved:parport: Fix race between port and client registrationThe parport subsystem registers port devices before they are fullyinitialised, resulting in a race condition where client drivers suchas lp can attach to ports that are not completely initialised or evenbeing torn down.When the port and client drivers are built as modules and loadedaround the same time during boot, this occasionally results in acrash. I was able to make this happen reliably in a VM with aPC-style parallel port by patching parport_pc to fail probing:<spanclass="q">> --- a/drivers/parport/parport_pc.c> +++ b/drivers/parport/parport_pc.c> @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,> if (!p)> goto out3;>> -base_res = request_region(base, 3, p->name);> +base_res = NULL;> if (!base_res)> goto out4;>and then running: while true; do modprobe lp & modprobe parport_pcwaitrmmod lp parport_pc donefor a few seconds.In the long term I think port registration should be changed to putthe call to device_add() inside parport_announce_port(), but since thelatter currently cannot fail this will require changing all portdrivers.For now, add a flag to indicate whether a port has been "announced"and only try to attach client drivers to ports when the flag is set.The Linux kernel CVE team has assigned CVE-2026-63942 to this issue.
已分析 2.openEulerScore 7.8
已分析 3.openEulerVector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
已分析 4.受影响版本排查 master:不受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP3:受影响,openEuler-24.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-SP2:受影响
已分析 5.是否涉及abi变化 master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP3:否,openEuler-24.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-SP2:否
已分析 6.原因说明 master:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:不修复-超出修复范围,openEuler-22.03-LTS-SP4:漏洞仍在分析中,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-SP1:漏洞仍在分析中,openEuler-24.03-LTS-SP3:漏洞仍在分析中,openEuler-24.03-LTS-SP4:漏洞仍在分析中,openEuler-22.03-LTS-SP3:不修复-超出修复范围,openEuler-24.03-LTS:不修复-超出修复范围,openEuler-24.03-LTS-SP2:不修复-超出修复范围

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

likedislike
H
hulk-ci-bot成员
8月11日 评论：

CVE-2026-63942

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

parport: Fix race between port and client registration

The parport subsystem registers port devices before they are fully
initialised, resulting in a race condition where client drivers such
as lp can attach to ports that are not completely initialised or even
being torn down.

When the port and client drivers are built as modules and loaded
around the same time during boot, this occasionally results in a
crash. I was able to make this happen reliably in a VM with a
PC-style parallel port by patching parport_pc to fail probing:

> --- a/drivers/parport/parport_pc.c
> +++ b/drivers/parport/parport_pc.c
> @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,
> if (!p)
> goto out3;
>
> - base_res = request_region(base, 3, p->name);
> + base_res = NULL;
> if (!base_res)
> goto out4;
>

and then running:

while true; do
    modprobe lp &#38; modprobe parport_pc
wait
rmmod lp parport_pc
done

for a few seconds.

In the long term I think port registration should be changed to put
the call to device_add() inside parport_announce_port(), but since the
latter currently cannot fail this will require changing all port
drivers.

For now, add a flag to indicate whether a port has been "announced"
and only try to attach client drivers to ports when the flag is set.

The Linux kernel CVE team has assigned CVE-2026-63942 to this issue.

openEuler评分:(评分和向量)
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

受影响版本排查(受影响/不受影响):
1.master:不受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:受影响
5.openEuler-24.03-LTS:受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:受影响
8.openEuler-24.03-LTS-SP2:受影响
9.openEuler-24.03-LTS-SP3:受影响
10.openEuler-24.03-LTS-SP4:受影响

修复是否涉及abi变化(是/否)：
1.master:否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS-SP3:否
4.openEuler-22.03-LTS-SP4:否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-24.03-LTS-SP1:否
8.openEuler-24.03-LTS-SP2:否
9.openEuler-24.03-LTS-SP3:否
10.openEuler-24.03-LTS-SP4:否

原因说明：
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:暂不修复-暂无解决方案或补丁
3.openEuler-22.03-LTS-SP3:不修复-超出修复范围
4.openEuler-22.03-LTS-SP4:暂不修复-漏洞仍在分析中
5.openEuler-24.03-LTS:不修复-超出修复范围
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:正常修复
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:正常修复
10.openEuler-24.03-LTS-SP4:正常修复

likedislike
openeuler-ci-botopeneuler-ci-bot成员
8月11日 修改了issue 的描述
openeuler-ci-bot
openeuler-ci-bot成员
8月11日 评论：

@gitee-cmd, @zhujianwei001, @luoyukai, @kylincuilei, @tanjingguo, @tangjie, @mailofzxf, @zeng-wei2000, @Sam-Luo The CVE score needs to be reviewed (the review instruction /approve or /reject means agreement and rejection).

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
8月11日 评论：

@hulk-ci-bot ,请给出NVD评分和openEuler评分不一致的理由

likedislike
Zzhangxiaoxu
8月21日 关联了pull request：[OLK-5.10] Fix CVE-2026-63942
openeuler-ci-botopeneuler-ci-bot成员
9月1日 关闭了 issue
openeuler-ci-botopeneuler-ci-bot成员
9月1日 修改了issue 的描述
openeuler-ci-botopeneuler-ci-bot成员
9月1日 重新打开了 issue
openeuler-ci-botopeneuler-ci-bot成员
9月1日 issue状态由 进行中 改变为 待办的
openeuler-ci-bot
openeuler-ci-bot成员
9月1日 评论：

经过 cve-manager 解析 openEuler评分 已改变 需要您及时进行审核,以便maintainer进行后续操作.

likedislike
H
hulk-ci-bot成员
9月2日 评论：

CVE-2026-63942

影响性分析说明：
In the Linux kernel, the following vulnerability has been resolved:

parport: Fix race between port and client registration

The parport subsystem registers port devices before they are fully
initialised, resulting in a race condition where client drivers such
as lp can attach to ports that are not completely initialised or even
being torn down.

When the port and client drivers are built as modules and loaded
around the same time during boot, this occasionally results in a
crash. I was able to make this happen reliably in a VM with a
PC-style parallel port by patching parport_pc to fail probing:

> --- a/drivers/parport/parport_pc.c
> +++ b/drivers/parport/parport_pc.c
> @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,
> if (!p)
> goto out3;
>
> - base_res = request_region(base, 3, p->name);
> + base_res = NULL;
> if (!base_res)
> goto out4;
>

and then running:

while true; do
    modprobe lp &#38; modprobe parport_pc
wait
rmmod lp parport_pc
done

for a few seconds.

In the long term I think port registration should be changed to put
the call to device_add() inside parport_announce_port(), but since the
latter currently cannot fail this will require changing all port
drivers.

For now, add a flag to indicate whether a port has been "announced"
and only try to attach client drivers to ports when the flag is set.

The Linux kernel CVE team has assigned CVE-2026-63942 to this issue.

openEuler评分:(评分和向量)
7.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

受影响版本排查(受影响/不受影响):
1.master:不受影响
2.openEuler-20.03-LTS-SP4:受影响
3.openEuler-22.03-LTS-SP3:受影响
4.openEuler-22.03-LTS-SP4:受影响
5.openEuler-24.03-LTS:受影响
6.openEuler-24.03-LTS-Next:不受影响
7.openEuler-24.03-LTS-SP1:受影响
8.openEuler-24.03-LTS-SP2:受影响
9.openEuler-24.03-LTS-SP3:受影响
10.openEuler-24.03-LTS-SP4:受影响

修复是否涉及abi变化(是/否)：
1.master:否
2.openEuler-20.03-LTS-SP4:否
3.openEuler-22.03-LTS-SP3:否
4.openEuler-22.03-LTS-SP4:否
5.openEuler-24.03-LTS:否
6.openEuler-24.03-LTS-Next:否
7.openEuler-24.03-LTS-SP1:否
8.openEuler-24.03-LTS-SP2:否
9.openEuler-24.03-LTS-SP3:否
10.openEuler-24.03-LTS-SP4:否

原因说明：
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:暂不修复-暂无解决方案或补丁
3.openEuler-22.03-LTS-SP3:不修复-超出修复范围
4.openEuler-22.03-LTS-SP4:正常修复
5.openEuler-24.03-LTS:不修复-超出修复范围
6.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
7.openEuler-24.03-LTS-SP1:正常修复
8.openEuler-24.03-LTS-SP2:不修复-超出修复范围
9.openEuler-24.03-LTS-SP3:正常修复
10.openEuler-24.03-LTS-SP4:正常修复

likedislike
openeuler-ci-botopeneuler-ci-bot成员
9月2日 修改了issue 的描述
openeuler-ci-bot
openeuler-ci-bot成员
9月2日 评论：

@GongLei- 经过 cve-manager 解析, 已分析的内容如下表所示:

状态 分析项目 内容
已分析 1.影响性分析说明 In the Linux kernel, the following vulnerability has been resolved:parport: Fix race between port and client registrationThe parport subsystem registers port devices before they are fullyinitialised, resulting in a race condition where client drivers suchas lp can attach to ports that are not completely initialised or evenbeing torn down.When the port and client drivers are built as modules and loadedaround the same time during boot, this occasionally results in acrash. I was able to make this happen reliably in a VM with aPC-style parallel port by patching parport_pc to fail probing:<spanclass="q">> --- a/drivers/parport/parport_pc.c> +++ b/drivers/parport/parport_pc.c> @@ -2069,7 +2069,7 @@ static struct parport *__parport_pc_probe_port(unsigned long int base,> if (!p)> goto out3;>> -base_res = request_region(base, 3, p->name);> +base_res = NULL;> if (!base_res)> goto out4;>and then running: while true; do modprobe lp & modprobe parport_pcwaitrmmod lp parport_pc donefor a few seconds.In the long term I think port registration should be changed to putthe call to device_add() inside parport_announce_port(), but since thelatter currently cannot fail this will require changing all portdrivers.For now, add a flag to indicate whether a port has been "announced"and only try to attach client drivers to ports when the flag is set.The Linux kernel CVE team has assigned CVE-2026-63942 to this issue.
已分析 2.openEulerScore 7.8
已分析 3.openEulerVector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
已分析 4.受影响版本排查 master:不受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP3:受影响,openEuler-24.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-SP2:受影响
已分析 5.是否涉及abi变化 master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP3:否,openEuler-24.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-SP2:否
已分析 6.原因说明 master:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:暂不修复-暂无解决方案或补丁,openEuler-22.03-LTS-SP4:正常修复,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-SP1:正常修复,openEuler-24.03-LTS-SP3:正常修复,openEuler-24.03-LTS-SP4:正常修复,openEuler-22.03-LTS-SP3:不修复-超出修复范围,openEuler-24.03-LTS:不修复-超出修复范围,openEuler-24.03-LTS-SP2:不修复-超出修复范围

请确认分析内容的准确性, 确认无误后, 您可以进行后续步骤, 否则您可以继续分析.

likedislike
openeuler-ci-bot
openeuler-ci-bot成员
9月2日 评论：

经过cve-manager解析，部分分支PR未合入，如红色字体所示：

原因说明：
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:暂不修复-暂无解决方案或补丁
3.openEuler-22.03-LTS-SP4:正常修复(PR未合入)
4.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
5.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
6.openEuler-24.03-LTS-SP3:正常修复(PR未合入)
7.openEuler-24.03-LTS-SP4:正常修复(PR未合入)
8.openEuler-22.03-LTS-SP3:不修复-超出修复范围
9.openEuler-24.03-LTS:不修复-超出修复范围
10.openEuler-24.03-LTS-SP2:不修复-超出修复范围

likedislike
openeuler-ci-botopeneuler-ci-bot成员
9月2日 issue状态由 待办的 改变为 进行中
openeuler-ci-botopeneuler-ci-bot成员
9月7日 关闭了 issue
openeuler-ci-bot
openeuler-ci-bot成员
9月7日 评论：

经过cve-manager解析，部分分支PR未合入，如红色字体所示：

原因说明：
1.master:不受影响-漏洞代码不能被攻击者触发
2.openEuler-20.03-LTS-SP4:暂不修复-暂无解决方案或补丁
3.openEuler-22.03-LTS-SP4:正常修复
4.openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发
5.openEuler-24.03-LTS-SP1:正常修复(PR未合入)
6.openEuler-24.03-LTS-SP3:正常修复(PR未合入)
7.openEuler-24.03-LTS-SP4:正常修复(PR未合入)
8.openEuler-22.03-LTS-SP3:不修复-超出修复范围
9.openEuler-24.03-LTS:不修复-超出修复范围
10.openEuler-24.03-LTS-SP2:不修复-超出修复范围

likedislike
openeuler-ci-botopeneuler-ci-bot成员
9月7日 重新打开了 issue
openeuler-ci-botopeneuler-ci-bot成员
9月14日 issue状态由 进行中 改变为 待办的