Web This site Trusted
18 result(s) for “okapi bm25 site www eyespy cy site www is gov site does nvidia com site can site:cdn.kernel.org” · 855 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.
Freshness: no result on this page carries a fetch time yet (indexed before the fetch epoch was stored beside the doc)
This dynamic allocation is problematic because: - It can fail, especially at the fscrypt_destroy_inline_crypt_key() call site when it's invoked for inode eviction under direct reclaim
from the top result below
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.101
Contrary to what was stated on d36349ea73d8 ("Bluetooth: hci_conn: Fix running bis_cleanup for hci_conn->type PA_LINK") the PA_LINK does in fact needs to run bis_cleanup in order to terminate the PA Sync, since that is bond to the listening socket which is the entity that controls the lifetime of PA Sync, so if it is
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.148
This, however, does not apply to the first time begin_cpu_udmabuf() is called on an udmabuf, in which case the implementation previously relied on get_sg_table() to perform the cache synchronisation
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.152
A malicious or malformed Thunderbolt device can set dual_link_port_nr beyond the allocated sw->ports[] (max_port_number + 1 entries), producing an out-of-bounds tb_port pointer that is stored and later dereferenced
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.104
A malicious or malformed Thunderbolt device can set dual_link_port_nr beyond the allocated sw->ports[] (max_port_number + 1 entries), producing an out-of-bounds tb_port pointer that is stored and later dereferenced
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.42
If the work is already running, mark it cancelled and let the worker own the cleanup; otherwise tcm_disable() can cancel the queued work and clean up immediately
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.45
A malicious or malformed Thunderbolt device can set dual_link_port_nr beyond the allocated sw->ports[] (max_port_number + 1 entries), producing an out-of-bounds tb_port pointer that is stored and later dereferenced
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.46
Every other external pin is left at 0x411111f0, so the headset mic pin 0x19 is never parsed and no headset mic input exists
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.1.9
A malicious or malformed Thunderbolt device can set dual_link_port_nr beyond the allocated sw->ports[] (max_port_number + 1 entries), producing an out-of-bounds tb_port pointer that is stored and later dereferenced
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.266
local_read(&cpu_buffer->committing)) // triggers warning The committing counter can temporarily drop to 0 during a single write operation (within rb_move_tail), creating a window where swap can succeed even though the write is still in progress
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.6.157
Nathan Tested-by: Ron Economos Tested-by: Miguel Ojeda Tested-by: Francesco Dolcini Signed-off-by: Greg Kroah-Hartman commit 32e598324edc3ebb1ac9362d5b9fc30ce0de4873 Author: Xixin Liu Date: Thu Aug 13 14:42:01 2026 +0800 nvmet-rdma: fix queue leak when connect backlog is exceeded commit
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.216
A malicious or malformed Thunderbolt device can set dual_link_port_nr beyond the allocated sw->ports[] (max_port_number + 1 entries), producing an out-of-bounds tb_port pointer that is stored and later dereferenced
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.265
A malicious or malformed Thunderbolt device can set dual_link_port_nr beyond the allocated sw->ports[] (max_port_number + 1 entries), producing an out-of-bounds tb_port pointer that is stored and later dereferenced
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.183
A malicious or malformed Thunderbolt device can set dual_link_port_nr beyond the allocated sw->ports[] (max_port_number + 1 entries), producing an out-of-bounds tb_port pointer that is stored and later dereferenced
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.2.5
Still, this is a clear bug that is better to be fixed, and can be easily fixed
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.18.50
The fix is made to be backport-friendly: the cleaner fix would be to perhaps pass the hstate to huge_ptep_get() - that is wider churn and we can do that later
https://cdn.kernel.org/pub/linux/kernel/v7.x/ChangeLog-7.2.6
Moreover, d9c56501c72fd ("net: tcp: block mixing readable and unreadable frags") relies on that and assumes that the devmem binding is present IFF we're using the zero-copy path, which can be used to mix net-iov and pages in a single skb, and break invariants
https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.153
local_read(&cpu_buffer->committing)) // triggers warning The committing counter can temporarily drop to 0 during a single write operation (within rb_move_tail), creating a window where swap can succeed even though the write is still in progress