In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
A vulnerability was found in Linux Kernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As an impact it is known to affect confidentiality, integrity, and availability.Upgrading to version 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability. Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
A vulnerability was found in Linux Kernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As an impact it is known to affect confidentiality, integrity, and availability.Upgrading to version 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability. Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
A vulnerability was found in Linux Kernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As an impact it is known to affect confidentiality, integrity, and availability.Upgrading to version 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability. Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
A vulnerability was found in Linux Kernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As an impact it is known to affect confidentiality, integrity, and availability.Upgrading to version 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability. Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
A vulnerability was found in Linux Kernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As an impact it is known to affect confidentiality, integrity, and availability.Upgrading to version 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability. Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
A vulnerability was found in Linux Kernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As an impact it is known to affect confidentiality, integrity, and availability.Upgrading to version 5.10.240, 5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability. Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53The Linux kernel CVE team has assigned CVE-2025-38461 to this issue.
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53The Linux kernel CVE team has assigned CVE-2025-38461 to this issue.
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53The Linux kernel CVE team has assigned CVE-2025-38461 to this issue.
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53The Linux kernel CVE team has assigned CVE-2025-38461 to this issue.
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53The Linux kernel CVE team has assigned CVE-2025-38461 to this issue.
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53The Linux kernel CVE team has assigned CVE-2025-38461 to this issue.
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53The Linux kernel CVE team has assigned CVE-2025-38461 to this issue.
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53The Linux kernel CVE team has assigned CVE-2025-38461 to this issue.
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53The Linux kernel CVE team has assigned CVE-2025-38461 to this issue.
A vulnerability was found in LinuxKernel up to 6.16-rc5 (Operating System). It has been declared as critical.The CWE definition for the vulnerability isCWE-119. The product performs operations on a memorybuffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.As animpact it is known to affect confidentiality, integrity, andavailability.Upgrading to version 5.10.240,5.15.189, 6.1.146, 6.6.99, 6.12.39, 6.15.7 or 6.16-rc6 eliminates this vulnerability.Applying the patch 8667e8d0eb46bc54fdae30ba2f4786407d3d88eb/36a439049b34cca0b3661276049b84a1f76cc21a/9ce53e744f18e73059d3124070e960f3aa9902bf/9d24bb6780282b0255b9929abe5e8f98007e2c6e/ae2c712ba39c7007de63cb0c75b51ce1caaf1da5/7b73bddf54777fb62d4d8c7729d0affe6df04477/687aa0c5581b8d4aa87fd92973e4ee576b550cdf is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53The Linux kernel CVE team has assigned CVE-2025-38461 to this issue.
In the Linux kernel, the followingvulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protectnew_transportfrom becoming a stale pointer.This alsotakes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault foraddress: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP:0010:vsock_assign_transport+0x366/0x600CallTrace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53
In the Linux kernel, the following vulnerability has been resolved:vsock: Fix transport_* TOCTOUTransport assignment may race with module unload. Protect new_transportfrom becoming a stale pointer.This also takes care of an insecure call in vsock_use_local_transport();add a lockdep assert.BUG: unable to handle page fault for address: fffffbfff8056000Oops: Oops: 0000 [#1] SMP KASANRIP: 0010:vsock_assign_transport+0x366/0x600Call Trace: vsock_connect+0x59c/0xc40 __sys_connect+0xe8/0x100 __x64_sys_connect+0x6e/0xc0 do_syscall_64+0x92/0x1c0 entry_SYSCALL_64_after_hwframe+0x4b/0x53The Linux kernel CVE team has assigned CVE-2025-38461 to this issue.
