Open
CVE-2025-22077 #10781
openeuler-ci-botAdd on  Apr 17, 2025
openeuler-ci-bot
openeuler-ci-botCollaborators
Apr 17, 2025 Create

一、漏洞信息
漏洞编号:CVE-2025-22077
漏洞归属组件:kernel
漏洞归属的版本:4.19.140,4.19.194,4.19.90,5.10.0,6.1.19,6.4.0,6.6.0
CVSS评分:
BaseScore:5.5 Medium
Vector:CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
漏洞简述:
In the Linux kernel, the following vulnerability has been resolved:Revert smb: client: fix TCP timers deadlock after rmmod This reverts commit e9f2517a3e18a54a3943c098d2226b245d488801.Commit e9f2517a3e18 ( smb: client: fix TCP timers deadlock afterrmmod ) is intended to fix a null-ptr-deref in LOCKDEP, which ismentioned as CVE-2024-54680, but is actually did not fix anything;The issue can be reproduced on top of it. [0]Also, it reverted the change by commit ef7134c7fc48 ( smb: client:Fix use-after-free of network namespace. ) and introduced a realissue by reviving the kernel TCP socket.When a reconnect happens for a CIFS connection, the socket statetransitions to FIN_WAIT_1. Then, inet_csk_clear_xmit_timers_sync()in tcp_close() stops all timers for the socket.If an incoming FIN packet is lost, the socket will stay at FIN_WAIT_1forever, and such sockets could be leaked up to net.ipv4.tcp_max_orphans.Usually, FIN can be retransmitted by the peer, but if the peer abortsthe connection, the issue comes into reality.I warned about this privately by pointing out the exact report [1],but the bogus fix was finally merged.So, we should not stop the timers to finally kill the connection onour side in that case, meaning we must not use a kernel socket forTCP whose sk->sk_net_refcnt is 0.The kernel socket does not have a reference to its netns to make itpossible to tear down netns without cleaning up every resource in it.For example, tunnel devices use a UDP socket internally, but we candestroy netns without removing such devices and let it completeduring exit. Otherwise, netns would be leaked when the last applicationdied.However, this is problematic for TCP sockets because TCP has timers toclose the connection gracefully even after the socket is close()d. Thelifetime of the socket and its netns is different from the lifetime ofthe underlying connection.If the socket user does not maintain the netns lifetime, the timer couldbe fired after the socket is close()d and its netns is freed up, resultingin use-after-free.Actually, we have seen so many similar issues and converted such socketsto have a reference to netns.That s why I converted the CIFS client socket to have a reference tonetns (sk->sk_net_refcnt == 1), which is somehow mentioned as out-of-scopeof CIFS and technically wrong in e9f2517a3e18, but is in-scope and rightfix.Regarding the LOCKDEP issue, we can prevent the module unload bybumping the module refcount when switching the LOCKDDEP key insock_lock_init_class_and_name(). [2]For a while, let s revert the bogus fix.Note that now we can use sk_net_refcnt_upgrade() for the socketconversion, but I ll do so later separately to make backport easy.
漏洞公开时间:2025-04-16 23:16:01
漏洞创建时间:2025-04-17 00:34:15
漏洞详情参考链接:
https://nvd.nist.gov/vuln/detail/CVE-2025-22077

更多参考(点击展开)
参考来源 参考链接 来源链接
416baaa9-dc9f-4396-8d5f-8c081fb06d67 https://git.kernel.org/stable/c/4b6f6bf1bde8d6045c389fda8d21c304dfe49384
416baaa9-dc9f-4396-8d5f-8c081fb06d67 https://git.kernel.org/stable/c/8dbf060480236877703bff0106fc984576184d11
416baaa9-dc9f-4396-8d5f-8c081fb06d67 https://git.kernel.org/stable/c/95d2b9f693ff2a1180a23d7d59acc0c4e72f4c41
416baaa9-dc9f-4396-8d5f-8c081fb06d67 https://git.kernel.org/stable/c/f761eeefd531e6550cd3a5c047835b4892acb00d
suse_bugzilla http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2025-22077 https://bugzilla.suse.com/show_bug.cgi?id=1241403
suse_bugzilla https://www.cve.org/CVERecord?id=CVE-2025-22077 https://bugzilla.suse.com/show_bug.cgi?id=1241403
suse_bugzilla https://git.kernel.org/stable/c/476617a4ca0123f0df677d547a82a110c27c8c74 https://bugzilla.suse.com/show_bug.cgi?id=1241403
suse_bugzilla https://git.kernel.org/stable/c/4e7f1644f2ac6d01dc584f6301c3b1d5aac4eaef https://bugzilla.suse.com/show_bug.cgi?id=1241403
suse_bugzilla https://git.kernel.org/stable/c/7d8dfc27d90d41627c0d6ada97ed0ab57b3dae25 https://bugzilla.suse.com/show_bug.cgi?id=1241403
suse_bugzilla https://git.kernel.org/stable/c/961755d0055e0e96d1849cc0425da966c8a64e53 https://bugzilla.suse.com/show_bug.cgi?id=1241403
suse_bugzilla https://git.kernel.org/stable/c/c6b6b8dcef4adf8ee4e439bb97e74106096c71b8 https://bugzilla.suse.com/show_bug.cgi?id=1241403
suse_bugzilla https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2025/CVE-2025-22077.mbox https://bugzilla.suse.com/show_bug.cgi?id=1241403
redhat_bugzilla https://lore.kernel.org/linux-cve-announce/2025041612-CVE-2025-22077-d534@gregkh/T https://bugzilla.redhat.com/show_bug.cgi?id=2360283
anolis https://anas.openanolis.cn/cves/detail/CVE-2025-22077
mageia http://advisories.mageia.org/MGASA-2025-0142.html
osv https://git.kernel.org/stable/c/4b6f6bf1bde8d6045c389fda8d21c304dfe49384 https://osv.dev/vulnerability/CVE-2025-22077
osv https://git.kernel.org/stable/c/8dbf060480236877703bff0106fc984576184d11 https://osv.dev/vulnerability/CVE-2025-22077
osv https://git.kernel.org/stable/c/95d2b9f693ff2a1180a23d7d59acc0c4e72f4c41 https://osv.dev/vulnerability/CVE-2025-22077
osv https://git.kernel.org/stable/c/f761eeefd531e6550cd3a5c047835b4892acb00d https://osv.dev/vulnerability/CVE-2025-22077
osv https://security-tracker.debian.org/tracker/CVE-2025-22077 https://osv.dev/vulnerability/CVE-2025-22077

漏洞分析指导链接:
https://atomgit.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
漏洞数据来源:
openBrain开源漏洞感知系统
漏洞补丁信息:

详情(点击展开)
影响的包 修复版本 修复补丁 问题引入补丁 来源
linux_kernel 6.6.87 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c6b6b8dcef4adf8ee4e439bb97e74106096c71b8 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e8c71494181153a134c96da28766a57bd1eac8cb linuxkernelcves
linux_kernel 6.12.23 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7d8dfc27d90d41627c0d6ada97ed0ab57b3dae25 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e8c71494181153a134c96da28766a57bd1eac8cb linuxkernelcves
linux_kernel 6.13.11 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=961755d0055e0e96d1849cc0425da966c8a64e53 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e8c71494181153a134c96da28766a57bd1eac8cb linuxkernelcves
linux_kernel 6.14.2 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=476617a4ca0123f0df677d547a82a110c27c8c74 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e8c71494181153a134c96da28766a57bd1eac8cb linuxkernelcves
linux_kernel 6.15-rc1 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4e7f1644f2ac6d01dc584f6301c3b1d5aac4eaef https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e8c71494181153a134c96da28766a57bd1eac8cb linuxkernelcves

二、漏洞分析结构反馈
影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:smb: client: Fix netns refcount imbalance causing leaks and use-after-freeCommit ef7134c7fc48 ("smb: client: Fix use-after-free of networknamespace.") attempted to fix a netns use-after-free issue by manuallyadjusting reference counts via sk->sk_net_refcnt and sock_inuse_add().However, a later commit e9f2517a3e18 ("smb: client: fix TCP timers deadlockafter rmmod") pointed out that the approach of manually settingsk->sk_net_refcnt in the first commit was technically incorrect, assk->sk_net_refcnt should only be set for user sockets. It led to issueslike TCP timers not being cleared properly on close. The second commitmoved to a model of just holding an extra netns reference forserver->ssocket using get_net(), and dropping it when the server is torndown.But there remain some gaps in the get_net()/put_net() balancing added bythese commits. The incomplete reference handling in these fixes resultsin two issues:1. Netns refcount leaks[1]The problem process is as follows:mount.cifs cifsdcifs_do_mount cifs_mount cifs_mount_get_session cifs_get_tcp_session get_net() /* First get net. */ ip_connect generic_ip_connect /* Try port 445 */ get_net() ->connect() /* Failed */ put_net() generic_ip_connect /* Try port 139 */ get_net() /* Missing matching put_net() for this get_net().*/ cifs_get_smb_ses cifs_negotiate_protocol smb2_negotiate SMB2_negotiate cifs_send_recv wait_for_response cifs_demultiplex_thread cifs_read_from_socket cifs_readv_from_socket cifs_reconnect cifs_abort_connection sock_release(); server->ssocket = NULL; /* Missing put_net() here. */ generic_ip_connect get_net() ->connect() /* Failed */ put_net() sock_release(); server->ssocket = NULL; free_rsp_buf ... clean_demultiplex_info /* It's only called once here. */ put_net()When cifs_reconnect() is triggered, the server->ssocket is releasedwithout a corresponding put_net() for the reference acquired ingeneric_ip_connect() before. it ends up calling generic_ip_connect()again to retry get_net(). After that, server->ssocket is set to NULLin the error path of generic_ip_connect(), and the net count cannot bereleased in the final clean_demultiplex_info() function.2. Potential use-after-freeThe current refcounting scheme can lead to a potential use-after-free issuein the following scenario: cifs_do_mount cifs_mount cifs_mount_get_session cifs_get_tcp_session get_net() /* First get net */ ip_connect generic_ip_connect get_net() bind_socket kernel_bind /* failed */ put_net() /* after out_err_crypto_release label */ put_net() /* after out_err label */ put_net()In the exception handling process where binding the socket fails, theget_net() and put_net() calls are unbalanced, which may cause theserver->net reference count to drop to zero and be prematurely released.To address both issues, this patch ties the netns reference counting tothe server->ssocket and server lifecycles. The extra reference is nowacquired when the server or socket is created, and released when thesocket is destroye
openEuler评分:
5.5
Vector:CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
受影响版本排查(受影响/不受影响):
1.master(6.18.18):不受影响
2.openEuler-20.03-LTS-SP4(4.19.90):受影响
3.openEuler-22.03-LTS-SP3(5.10.0):受影响
4.openEuler-22.03-LTS-SP4(5.10.0):受影响
5.openEuler-24.03-LTS(6.6.0):受影响
6.openEuler-24.03-LTS-Next(6.6.0):不受影响
7.openEuler-24.03-LTS-SP1(6.6.0):受影响
8.openEuler-24.03-LTS-SP2(6.6.0):受影响
9.openEuler-24.03-LTS-SP3(6.6.0):不受影响

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

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

likedislike
openeuler-ci-botopeneuler-ci-botCollaborators
Apr 17, 2025 添加了   CVE/UNFIXED 标签
openeuler-ci-botopeneuler-ci-botCollaborators
Apr 17, 2025 创建了CVE和安全问题
openeuler-ci-bot
openeuler-ci-botCollaborators
Apr 17, 2025 Comments:

Hi openeuler-ci-bot, welcome to the openEuler Community.
I'm the Bot here serving you. You can find the instructions on how to interact with me at Here.
If you have any questions, please contact the SIG: Kernel, and any of the maintainers.

likedislike
openeuler-ci-bot
openeuler-ci-botCollaborators
Apr 17, 2025 Comments:

@yangyingliang ,@jiaoff ,@guohaocs2c ,@hanjun-guo ,@woqidaideshi ,@newbeats ,@zhangyi089 ,@colyli ,@thundertown ,@htforge ,@chiqijun ,@lengchao ,@zhujianwei001 ,@kylin-mayukun ,@wangxiongfeng ,@wkfxxx ,@SuperSix173 ,@jentlestea ,@oskernel0719 ,@gasonchen
issue处理注意事项:
1. 当前issue受影响的分支提交pr时, 须在pr描述中填写当前issue编号进行关联, 否则无法关闭当前issue;
2. 模板内容需要填写完整, 无论是受影响或者不受影响都需要填写完整内容,未引入的分支不需要填写, 否则无法关闭当前issue;
3. 以下为模板中需要填写完整的内容, 请复制到评论区回复, 注: 内容的标题名称(影响性分析说明, openEuler评分, 受影响版本排查(受影响/不受影响), 修复是否涉及abi变化(是/否), 原因说明)不能省略,省略后cve-manager将无法正常解析填写内容.


影响性分析说明:

openEuler评分: (评分和向量)

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

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

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


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

分支状态 原因说明
受影响 正常修复
受影响 暂不修复-漏洞仍在分析中
受影响 暂不修复-暂无解决方案或补丁
受影响 暂不修复-待升级版本修复
受影响 不修复-超出修复范围
受影响 不修复-特殊原因导致不再修复
不受影响 不受影响-组件不存在
不受影响 不受影响-已有内置的内联控制或缓解措施
不受影响 不受影响-漏洞代码不能被攻击者触发
不受影响 不受影响-漏洞代码不在执行路径
不受影响 不受影响-漏洞代码不存在

issue处理具体操作请参考:
https://gitee.com/openeuler/cve-manager/blob/master/cve-vulner-manager/doc/md/manual.md
pr关联issue具体操作请参考:
https://gitee.com/help/articles/4142

likedislike
openeuler-ci-botopeneuler-ci-botCollaborators
Apr 17, 2025 添加了   sig/Kernel 标签
openeuler-ci-bot
openeuler-ci-botCollaborators
Apr 17, 2025 Comments:
参考网址 关联pr 状态 补丁链接
https://nvd.nist.gov/vuln/detail/CVE-2025-22077NoneNonehttps://git.kernel.org/stable/c/7d8dfc27d90d41627c0d6ada97ed0ab57b3dae25
https://git.kernel.org/stable/c/961755d0055e0e96d1849cc0425da966c8a64e53
https://git.kernel.org/stable/c/4e7f1644f2ac6d01dc584f6301c3b1d5aac4eaef
https://git.kernel.org/stable/c/476617a4ca0123f0df677d547a82a110c27c8c74
https://git.kernel.org/stable/c/c6b6b8dcef4adf8ee4e439bb97e74106096c71b8
https://ubuntu.com/security/CVE-2025-22077
https://www.opencve.io/cve/CVE-2025-22077
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2025-22077
https://security-tracker.debian.org/tracker/CVE-2025-22077NoneNonehttps://git.kernel.org/linus/4e7f1644f2ac6d01dc584f6301c3b1d5aac4eaef
http://www.cnnvd.org.cn/web/vulnerability/queryLds.tag?qcvCnnvdid=CVE-2025-22077

说明:补丁链接仅供初步排查参考,实际可用性请人工再次确认,补丁下载验证可使用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-botCollaborators
Apr 19, 2025 修改了描述
23 event messages are collapsed here。 See more
openeuler-ci-botopeneuler-ci-botCollaborators
Nov 10, 2025 修改了描述
hulk-ci-botCollaborators
Jan 26 Comments:

CVE-2025-22077

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

smb: client: Fix netns refcount imbalance causing leaks and use-after-free

Commit ef7134c7fc48 ("smb: client: Fix use-after-free of network
namespace.") attempted to fix a netns use-after-free issue by manually
adjusting reference counts via sk->sk_net_refcnt and sock_inuse_add().

However, a later commit e9f2517a3e18 ("smb: client: fix TCP timers deadlock
after rmmod") pointed out that the approach of manually setting
sk->sk_net_refcnt in the first commit was technically incorrect, as
sk->sk_net_refcnt should only be set for user sockets. It led to issues
like TCP timers not being cleared properly on close. The second commit
moved to a model of just holding an extra netns reference for
server->ssocket using get_net(), and dropping it when the server is torn
down.

But there remain some gaps in the get_net()/put_net() balancing added by
these commits. The incomplete reference handling in these fixes results
in two issues:

  1. Netns refcount leaks[1]

The problem process is as follows:

mount.cifs                        cifsd

cifs_do_mount
  cifs_mount
    cifs_mount_get_session
      cifs_get_tcp_session
        get_net()  /* First get net. */
        ip_connect
          generic_ip_connect /* Try port 445 */
            get_net()
            ->connect() /* Failed */
            put_net()
          generic_ip_connect /* Try port 139 */
            get_net() /* Missing matching put_net() for this get_net().*/
      cifs_get_smb_ses
        cifs_negotiate_protocol
          smb2_negotiate
            SMB2_negotiate
              cifs_send_recv
                wait_for_response
                                 cifs_demultiplex_thread
                                   cifs_read_from_socket
                                     cifs_readv_from_socket
                                       cifs_reconnect
                                         cifs_abort_connection
                                           sock_release();
                                           server->ssocket = NULL;
                                           /* Missing put_net() here. */
                                           generic_ip_connect
                                             get_net()
                                             ->connect() /* Failed */
                                             put_net()
                                             sock_release();
                                             server->ssocket = NULL;
          free_rsp_buf
    ...
                                   clean_demultiplex_info
                                     /* It's only called once here. */
                                     put_net()

When cifs_reconnect() is triggered, the server->ssocket is released
without a corresponding put_net() for the reference acquired in
generic_ip_connect() before. it ends up calling generic_ip_connect()
again to retry get_net(). After that, server->ssocket is set to NULL
in the error path of generic_ip_connect(), and the net count cannot be
released in the final clean_demultiplex_info() function.

  1. Potential use-after-free

The current refcounting scheme can lead to a potential use-after-free issue
in the following scenario:

 cifs_do_mount
   cifs_mount
     cifs_mount_get_session
       cifs_get_tcp_session
         get_net()  /* First get net */
           ip_connect
             generic_ip_connect
               get_net()
               bind_socket
	         kernel_bind /* failed */
               put_net()
         /* after out_err_crypto_release label */
         put_net()
         /* after out_err label */
         put_net()

In the exception handling process where binding the socket fails, the
get_net() and put_net() calls are unbalanced, which may cause the
server->net reference count to drop to zero and be prematurely released.

To address both issues, this patch ties the netns reference counting to
the server->ssocket and server lifecycles. The extra reference is now
acquired when the server or socket is created, and released when the
socket is destroyed or the server is torn down.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=219792

The Linux kernel CVE team has assigned CVE-2025-22077 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(6.1.0):不受影响
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:不受影响

修复是否涉及abi变化(是/否):
1.master(6.1.0):否
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:否

原因说明:
1.master(23.08.5):不受影响-漏洞代码不能被攻击者触发
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:不受影响-漏洞代码不能被攻击者触发

likedislike
openeuler-ci-botopeneuler-ci-botCollaborators
Jan 26 Modify description of issue
openeuler-ci-bot
openeuler-ci-botCollaborators
Jan 26 Comments:

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

状态 分析项目 内容
已分析 1.影响性分析说明 In the Linux kernel, the following vulnerability has been resolved:smb: client: Fix netns refcount imbalance causing leaks and use-after-freeCommit ef7134c7fc48 ("smb: client: Fix use-after-free of networknamespace.") attempted to fix a netns use-after-free issue by manuallyadjusting reference counts via sk->sk_net_refcnt and sock_inuse_add().However, a later commit e9f2517a3e18 ("smb: client: fix TCP timers deadlockafter rmmod") pointed out that the approach of manually settingsk->sk_net_refcnt in the first commit was technically incorrect, assk->sk_net_refcnt should only be set for user sockets. It led to issueslike TCP timers not being cleared properly on close. The second commitmoved to a model of just holding an extra netns reference forserver->ssocket using get_net(), and dropping it when the server is torndown.But there remain some gaps in the get_net()/put_net() balancing added bythese commits. The incomplete reference handling in these fixes resultsin two issues:1. Netns refcount leaks[1]The problem process is as follows:mount.cifs cifsdcifs_do_mount cifs_mount cifs_mount_get_session cifs_get_tcp_session get_net() /* First get net. */ ip_connect generic_ip_connect /* Try port 445 */ get_net() -&gt;connect() /* Failed */ put_net() generic_ip_connect /* Try port 139 */ get_net() /* Missing matching put_net() for this get_net().*/ cifs_get_smb_ses cifs_negotiate_protocol smb2_negotiate SMB2_negotiate cifs_send_recv wait_for_response cifs_demultiplex_thread cifs_read_from_socket cifs_readv_from_socket cifs_reconnect cifs_abort_connection sock_release(); server-&gt;ssocket = NULL; /* Missing put_net() here. */ generic_ip_connect get_net() -&gt;connect() /* Failed */ put_net() sock_release(); server-&gt;ssocket = NULL; free_rsp_buf ... clean_demultiplex_info /* It&#39;s only called once here. */ put_net()When cifs_reconnect() is triggered, the server->ssocket is releasedwithout a corresponding put_net() for the reference acquired ingeneric_ip_connect() before. it ends up calling generic_ip_connect()again to retry get_net(). After that, server->ssocket is set to NULLin the error path of generic_ip_connect(), and the net count cannot bereleased in the final clean_demultiplex_info() function.2. Potential use-after-freeThe current refcounting scheme can lead to a potential use-after-free issuein the following scenario: cifs_do_mount cifs_mount cifs_mount_get_session cifs_get_tcp_session get_net() /* First get net */ ip_connect generic_ip_connect get_net() bind_socket kernel_bind /* failed */ put_net() /* after out_err_crypto_release label */ put_net() /* after out_err label */ put_net()In the exception handling process where binding the socket fails, theget_net() and put_net() calls are unbalanced, which may cause theserver->net reference count to drop to zero and be prematurely released.To address both issues, this patch ties the netns reference counting tothe server->ssocket and server lifecycles. The extra reference is nowacquired when the server or socket is created, and released when thesocket is destroyed or the server is torn down.[1]: <ahref="https://bugzilla.kernel.org/show_bug.cgi?id=219792">https://bugzilla.kernel.org/show_bug.cgi?id=219792The Linux kernel CVE team has assigned CVE-2025-22077 to this issue.
已分析 2.openEulerScore 5.5
已分析 3.openEulerVector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
已分析 4.受影响版本排查 master:不受影响,openEuler-20.03-LTS-SP4:受影响,openEuler-22.03-LTS-SP3:受影响,openEuler-22.03-LTS-SP4:受影响,openEuler-24.03-LTS:受影响,openEuler-24.03-LTS-Next:不受影响,openEuler-24.03-LTS-SP1:受影响,openEuler-24.03-LTS-SP2:受影响,openEuler-24.03-LTS-SP3:不受影响
已分析 5.是否涉及abi变化 master:否,openEuler-20.03-LTS-SP4:否,openEuler-22.03-LTS-SP3:否,openEuler-22.03-LTS-SP4:否,openEuler-24.03-LTS:否,openEuler-24.03-LTS-Next:否,openEuler-24.03-LTS-SP1:否,openEuler-24.03-LTS-SP2:否,openEuler-24.03-LTS-SP3:否
已分析 6.原因说明 master:不受影响-漏洞代码不能被攻击者触发,openEuler-20.03-LTS-SP4:正常修复,openEuler-22.03-LTS-SP3:不修复-超出修复范围,openEuler-22.03-LTS-SP4:不修复-超出修复范围,openEuler-24.03-LTS:正常修复,openEuler-24.03-LTS-Next:不受影响-漏洞代码不能被攻击者触发,openEuler-24.03-LTS-SP1:正常修复,openEuler-24.03-LTS-SP2:正常修复,openEuler-24.03-LTS-SP3:不受影响-漏洞代码不能被攻击者触发

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

likedislike
openeuler-ci-bot
openeuler-ci-botCollaborators
Jan 26 Comments:

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

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

likedislike
openeuler-ci-botopeneuler-ci-botCollaborators
Jan 26 changed custom state from 待办的 to 进行中
hulk-ci-botCollaborators
May 21 Comments:

/check-issue

likedislike
openeuler-ci-bot
openeuler-ci-botCollaborators
May 21 Comments:

经过cve-manager解析,部分字段填写错误,如红色字体所示:

影响性分析说明:
In the Linux kernel, the following vulnerability has been resolved:smb: client: Fix netns refcount i...

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-botCollaborators
May 23 Modify description of issue