Web This site Trusted
30 result(s) for “if cram target site effort com site can kernel org site lemma would site:cdn.kernel.org” · 898 ms
Scope: Nishi’s own index (our crawl + Common Crawl) — not the whole live web. Some sites block all automated crawlers (anti-bot walls), so their pages may be absent here even though we never filter lawful content.
Did you mean if cam target site effort com site can kernel org site lemmy would site:cdn.kernel.org?
Freshness: no result on this page carries a fetch time yet (indexed before the fetch epoch was stored beside the doc)
So we can easily check if a machine had the CCS bug, when looking back over bug reports where we have the same machine with newer kernel
from the top result below
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.2.5
smb2_read_pipe() allocates only the payload size, so the alignment padding can expose up to seven bytes of uninitialized kernel heap memory
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.51
smb2_read_pipe() allocates only the payload size, so the alignment padding can expose up to seven bytes of uninitialized kernel heap memory
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.50
com Fixes: 5d2146a3354f ("selftests/mm: skip mlock tests if nobody user can't read it") Signed-off-by: Injae Ryou Cc: Brendan Jackman Cc: B
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.6
This missed the case where background I/O holds the final reference after userspace close() returns, and required explicit maintenance at each close-path site
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.266
However, there exists a race window where this check can be bypassed: ring_buffer_lock_reserve cpu_buffer = buffer->buffers[cpu]; // cpu_buffer_a rb_reserve_next_event rb_start_commit // inc committing if (unlikely(READ_ONCE(cpu_buffer->buffer)
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.183
With an authenticated peer, the reproducer triggered the same KASAN report in 2 of 2 unpatched runs on a KASAN-enabled netdev/main kernel: BUG: KASAN: slab-use-after-free in sctp_outq_select_transport Read of size 4 at addr ffff88800b9bd95c by task python3/197 Call Trace: sctp_outq_select_transport+0x549/0x8b0 [sctp]
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.2.6
org Tested-by: Brett A C Sheffield Tested-by: Salvatore Bonaccorso Tested-by: Ronald Warsow Tested-by: Takeshi Ogasawara Tested-by: Peter Schneider Tested-by: Benjamin Boortz Tested-by: Markus Reichelt Tested-by: Barry K
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.157
org/linux-kernel/5df6968a-2e5f-468e-b457-fc201535dd4c@linux
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.8
If the VUPDATE_NO_LOCK fires in that window, its handler would deliver a flip event to userspace before HW has latched to it
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.153
However, there exists a race window where this check can be bypassed: ring_buffer_lock_reserve cpu_buffer = buffer->buffers[cpu]; // cpu_buffer_a rb_reserve_next_event rb_start_commit // inc committing if (unlikely(READ_ONCE(cpu_buffer->buffer)
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.44
org Signed-off-by: Greg Kroah-Hartman Signed-off-by: Greg Kroah-Hartman commit 10be509fa8fd95d1e47d40d1f68b0b26dfe9d572 Author: Oliver Hartkopp Date: Fri Aug 7 09:52:11 2026 +0200 can: isotp: fix timer drain order, wakeup handling and tx_gen ordering commit 050f010f920da17c1044a4f174766ad553e770b6 upstream
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.46
org Tested-by: Pavel Machek (CIP) Tested-by: Brett A C Sheffield Tested-by: Florian Fainelli Tested-by: Barry K
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.265
With an authenticated peer, the reproducer triggered the same KASAN report in 2 of 2 unpatched runs on a KASAN-enabled netdev/main kernel: BUG: KASAN: slab-use-after-free in sctp_outq_select_transport Read of size 4 at addr ffff88800b9bd95c by task python3/197 Call Trace: sctp_outq_select_transport+0x549/0x8b0 [sctp]
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.216
With an authenticated peer, the reproducer triggered the same KASAN report in 2 of 2 unpatched runs on a KASAN-enabled netdev/main kernel: BUG: KASAN: slab-use-after-free in sctp_outq_select_transport Read of size 4 at addr ffff88800b9bd95c by task python3/197 Call Trace: sctp_outq_select_transport+0x549/0x8b0 [sctp]
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.13
Bridge a wired interface to an mt7925u AP and the first forwarded frame that arrives short panics the kernel: skbuff: skb_under_panic: len:415 put:4 tail:0x19b end:0x640 dev:wlan1 kernel BUG at net/core/skbuff
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.156
The interrupt URB buffer is allocated in setup_port_interrupt_in() based on the endpoint's wMaxPacketSize: buffer_size = usb_endpoint_maxp(epd); port->interrupt_in_buffer = kmalloc(buffer_size, GFP_KERNEL); When a USB device declares wMaxPacketSize = 8 on its interrupt IN endpoint, the buffer is allocated from kmalloc
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.184
However, there exists a race window where this check can be bypassed: ring_buffer_lock_reserve cpu_buffer = buffer->buffers[cpu]; // cpu_buffer_a rb_reserve_next_event rb_start_commit // inc committing if (unlikely(READ_ONCE(cpu_buffer->buffer)
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.151
org/drm/xe/kernel/-/work_items/8412 Tested-by: Alexander Kaplan Cc: Signed-off-by: Kai Vehmanen Link: https://patch
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.45
preferred_lft forever inet6 fe80::211:22ff:fe33:2255/64 scope link tentative proto kernel_ll valid_lft forever preferred_lft forever 6: eth1: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:22:22:33:22:55 brd ff:ff:ff:ff:ff:ff link-netns ns3 inet6 2001:db8:2::1/64 scope global nodad valid_lft
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.152
With an authenticated peer, the reproducer triggered the same KASAN report in 2 of 2 unpatched runs on a KASAN-enabled netdev/main kernel: BUG: KASAN: slab-use-after-free in sctp_outq_select_transport Read of size 4 at addr ffff88800b9bd95c by task python3/197 Call Trace: sctp_outq_select_transport+0x549/0x8b0 [sctp]
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.104
With an authenticated peer, the reproducer triggered the same KASAN report in 2 of 2 unpatched runs on a KASAN-enabled netdev/main kernel: BUG: KASAN: slab-use-after-free in sctp_outq_select_transport Read of size 4 at addr ffff88800b9bd95c by task python3/197 Call Trace: sctp_outq_select_transport+0x549/0x8b0 [sctp]
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.42
Otherwise, a built-in driver that tries to use the buddy allocator will run into a kernel NULL pointer dereference because slab_blocks is uninitialized
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.9
With an authenticated peer, the reproducer triggered the same KASAN report in 2 of 2 unpatched runs on a KASAN-enabled netdev/main kernel: BUG: KASAN: slab-use-after-free in sctp_outq_select_transport Read of size 4 at addr ffff88800b9bd95c by task python3/197 Call Trace: sctp_outq_select_transport+0x549/0x8b0 [sctp]
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.101
org Tested-by: Florian Fainelli Tested-by: Miguel Ojeda Tested-by: Peter Schneider Tested-by: Brett A C Sheffield Tested-by: Salvatore Bonaccorso Tested-by: Shuah Khan Tested-by: Pavel Machek (CIP) Tested-by: Mark Brown Tested-by: Harshit Mogalapalli Tested-by: Ron Economos Signed-off-by: Greg Kroah-Hartman commit
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.148
179936] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 [ 1
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.2.2
Two writes to a tap by an unprivileged user in its own userns are enough: kernel BUG at net/core/skbuff
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.155
Two writes to a tap by an unprivileged user in its own userns are enough: kernel BUG at net/core/skbuff
https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.18.50.tar.xz
yE3}-N?՝?$JQXFmUV+nȯ2=(=%ev ZK_;x#VlpvĻb^wg;_ Z^CWՕBزvhDTMְ /CqF`}3b68Ѽ 2*2,3ɖ\Œ9ZYpb` ګ7{P uspD$u ݑjSXl
https://cdn.kernel.org/pub/linux/kernel/v6.x/patch-6.1.184.xz
M.4R# ;Wy." "I!qpP;#cA:d_s~Ikb$ G X" XE Э^֬ >ffo /kGQR8E3: -4f]F rB/fIN UPuQgŞёLs`x Dq42bG"D^5{ _LS7į ߪv\
https://cdn.kernel.org/pub/linux/kernel/v6.x/incr/patch-6.12.104-105.xz
yTFĂ]Q hT^;cAMp24gu P&|gZ4bGRVRט pֳL8qSz2C%J7j [4+ES>I56$imv# AS$UF"4F,h :a5%TkpxzdBG8m)ZIAsҨ-b| ½Tt`