Forwarded from Knowledge Index
YouTube
Evolution of Music (2100 BC-2023 AD)
Timestamps:
Ancient Music (00:00)
Medieval Music (02:56)
Renaissance Music (05:29)
Baroque Music (07:24)
Classical Music (09:10)
Romantic Music (10:37)
Modernism/Popular Music (12:56)
Notes:
• Some years might be inaccurate.
• Only 1 song per artist/composer…
Ancient Music (00:00)
Medieval Music (02:56)
Renaissance Music (05:29)
Baroque Music (07:24)
Classical Music (09:10)
Romantic Music (10:37)
Modernism/Popular Music (12:56)
Notes:
• Some years might be inaccurate.
• Only 1 song per artist/composer…
Forwarded from /dev/stupid (Cicca 💤)
CVE-2024-44946
In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is blocked by sk_stream_wait_memory() 3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb and puts the skb to the write queue 4. Thread A faces an error and finally frees skb that is already in the write queue 5. kcm_release() does double-free the skb in the write queue When a thread is building a MSG_MORE skb, another thread must not touch it. Let's add a per-sk mutex and serialise kcm_sendmsg(). [0]: BUG: KASAN: slab-use-after-free in skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] BUG: KASAN: slab-use-after-free in skb_queue_purge include/linux/skbuff.h:3181 [inline] BUG: KASAN: slab-use-after-free in kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691 Read of size 8 at addr ffff0000ced0fc80 by task syz-executor329/6167 CPU: 1 PID: 6167 Comm: syz-executor329 Tainted: G B 6.8.0-rc5-syzkaller-g9abbc24128bc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:291 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:298 dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106 print_address_denoscription mm/kasan/report.c:377 [inline] print_report+0x178/0x518 mm/kasan/report.c:488 kasan_report+0xd8/0x138 mm/kasan/report.c:601 asan_report_load8_noabort+0x20/0x2c mm/kasan/report_generic.c:381 skb_unlink include/linux/skbuff.h:2366 [inline] skb_dequeue include/linux/skbuff.h:2385 [inline] skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] skb_queue_purge include/linux/skbuff.h:3181 [inline] kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691 sock_release net/socket.c:659 [inline] sock_close+0xa4/0x1e8 net/socket.c:1421 fput+0x30c/0x738 fs/file_table.c:376 __fput+0x20/0x30 fs/file_table.c:404 task_work_run+0x230/0x2e0 kernel/task_work.c:180 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0x618/0x1f64 kernel/exit.c:871 do_group_exit+0x194/0x22c kernel/exit.c:1020 get_signal+0x1500/0x15ec kernel/signal.c:2893 do_signal+0x23c/0x3b44 arch/arm64/kernel/signal.c:1249 do_notify_resume+0x74/0x1f4 arch/arm64/kernel/entry-common.c:148 exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline] exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline] el0_svc+0xac/0x168 arch/arm64/kernel/entry-common.c:713 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 Allocated by task 6166: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x40/0x78 mm/kasan/common.c:68 kasan_save_alloc_info+0x70/0x84 mm/kasan/generic.c:626 unpoison_slab_object mm/kasan/common.c:314 [inline] kasan_slab_alloc+0x74/0x8c mm/kasan/common.c:340 kasan_slab_alloc include/linux/kasan.h:201 [inline] slab_post_alloc_hook mm/slub.c:3813 [inline] slab_alloc_node mm/slub.c:3860 [inline] kmem_cache_alloc_node+0x204/0x4c0 mm/slub.c:3903 alloc_skb+0x19c/0x3d8 net/core/skbuff.c:641 alloc_skb include/linux/skbuff.h:1296 [inline] kcm_sendmsg+0x1d3c/0x2124 net/kcm/kcmsock.c:783 sock_sendmsg_nosec net/socket.c:730 [inline] sock_sendmsg net/socket.c:745 [inline] sock_sendmsg+0x220/0x2c0 net/socket.c:768 splice_to_socket+0x7cc/0xd58 fs/splice.c:889 do_splice_from fs/splice.c:941 [inline] direct_splice_actor+0xec/0x1d8 fs/splice.c:1164 splice_direct_to_actor+0x438/0xa0c fs/splice.c:1108 do_splice_direct_actor ---truncated---
https://github.com/Abdurahmon3236/CVE-2024-44946
In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is blocked by sk_stream_wait_memory() 3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb and puts the skb to the write queue 4. Thread A faces an error and finally frees skb that is already in the write queue 5. kcm_release() does double-free the skb in the write queue When a thread is building a MSG_MORE skb, another thread must not touch it. Let's add a per-sk mutex and serialise kcm_sendmsg(). [0]: BUG: KASAN: slab-use-after-free in skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] BUG: KASAN: slab-use-after-free in skb_queue_purge include/linux/skbuff.h:3181 [inline] BUG: KASAN: slab-use-after-free in kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691 Read of size 8 at addr ffff0000ced0fc80 by task syz-executor329/6167 CPU: 1 PID: 6167 Comm: syz-executor329 Tainted: G B 6.8.0-rc5-syzkaller-g9abbc24128bc #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/25/2024 Call trace: dump_backtrace+0x1b8/0x1e4 arch/arm64/kernel/stacktrace.c:291 show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:298 dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd0/0x124 lib/dump_stack.c:106 print_address_denoscription mm/kasan/report.c:377 [inline] print_report+0x178/0x518 mm/kasan/report.c:488 kasan_report+0xd8/0x138 mm/kasan/report.c:601 asan_report_load8_noabort+0x20/0x2c mm/kasan/report_generic.c:381 skb_unlink include/linux/skbuff.h:2366 [inline] skb_dequeue include/linux/skbuff.h:2385 [inline] skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] skb_queue_purge include/linux/skbuff.h:3181 [inline] kcm_release+0x170/0x4c8 net/kcm/kcmsock.c:1691 sock_release net/socket.c:659 [inline] sock_close+0xa4/0x1e8 net/socket.c:1421 fput+0x30c/0x738 fs/file_table.c:376 __fput+0x20/0x30 fs/file_table.c:404 task_work_run+0x230/0x2e0 kernel/task_work.c:180 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0x618/0x1f64 kernel/exit.c:871 do_group_exit+0x194/0x22c kernel/exit.c:1020 get_signal+0x1500/0x15ec kernel/signal.c:2893 do_signal+0x23c/0x3b44 arch/arm64/kernel/signal.c:1249 do_notify_resume+0x74/0x1f4 arch/arm64/kernel/entry-common.c:148 exit_to_user_mode_prepare arch/arm64/kernel/entry-common.c:169 [inline] exit_to_user_mode arch/arm64/kernel/entry-common.c:178 [inline] el0_svc+0xac/0x168 arch/arm64/kernel/entry-common.c:713 el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730 el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598 Allocated by task 6166: kasan_save_stack mm/kasan/common.c:47 [inline] kasan_save_track+0x40/0x78 mm/kasan/common.c:68 kasan_save_alloc_info+0x70/0x84 mm/kasan/generic.c:626 unpoison_slab_object mm/kasan/common.c:314 [inline] kasan_slab_alloc+0x74/0x8c mm/kasan/common.c:340 kasan_slab_alloc include/linux/kasan.h:201 [inline] slab_post_alloc_hook mm/slub.c:3813 [inline] slab_alloc_node mm/slub.c:3860 [inline] kmem_cache_alloc_node+0x204/0x4c0 mm/slub.c:3903 alloc_skb+0x19c/0x3d8 net/core/skbuff.c:641 alloc_skb include/linux/skbuff.h:1296 [inline] kcm_sendmsg+0x1d3c/0x2124 net/kcm/kcmsock.c:783 sock_sendmsg_nosec net/socket.c:730 [inline] sock_sendmsg net/socket.c:745 [inline] sock_sendmsg+0x220/0x2c0 net/socket.c:768 splice_to_socket+0x7cc/0xd58 fs/splice.c:889 do_splice_from fs/splice.c:941 [inline] direct_splice_actor+0xec/0x1d8 fs/splice.c:1164 splice_direct_to_actor+0x438/0xa0c fs/splice.c:1108 do_splice_direct_actor ---truncated---
https://github.com/Abdurahmon3236/CVE-2024-44946
GitHub
Abdurahmon3236/CVE-2024-44946
Contribute to Abdurahmon3236/CVE-2024-44946 development by creating an account on GitHub.
Forwarded from Compsci Library 📚 (Yb's)
Please open Telegram to view this post
VIEW IN TELEGRAM
YouTube
Electromagnetism as a Gauge Theory
"Why is electromagnetism a thing?" That's the question. In this video, we explore the answer given by gauge theory. In a nutshell, electromagnetism arises from local phase symmetry. But what does that mean, and how exactly does that work? That's what this…
Forwarded from Linux Academy
На конференции Open Source Summit China Линус Торвальдс обсудил текущее состояние и будущее ядра Linux. Он рассказал, что расширяемый планировщик sched_ext не будет включен в следующий релиз ядра, но ожидается его добавление в версии 6.12.
Он так же отметил отметил, что даже спустя 33 года разработки, базовые проблемы, такие как управление памятью, все еще актуальны.
Процесс разработки ядра стал более структурированным, с релизами каждые девять недель, а количество релизов не имеет значения. Обсуждая безопасность, он отметил, что уязвимости — это просто ошибки, и порекомендовал пользователям обновлять ядро для повышения безопасности.
Что касается внедрения языка Rust, Торвальдс выразил разочарование медленным темпом его принятия, объясняя это тем, что многие разработчики не знакомы с новым языком. Он также высказал скептицизм по поводу текущего хайпа вокруг ИИ, но надеется, что ИИ может помочь в ревью кода и обнаружении ошибок.
zdnet.com
@linuxacademiya
Please open Telegram to view this post
VIEW IN TELEGRAM
Isso aqui é foda pra cacete
Micron Technology
Micron Technology
YouTube
Inside Micron Taiwan’s Semiconductor Factory | Taiwan’s Mega Factories EP1
Join us for a tour of Micron Technology’s Taiwan chip manufacturing facilities to discover how chips are produced and how innovations in the semiconductor industry impact people and businesses all over the world.
Take a look inside one of the semiconductor…
Take a look inside one of the semiconductor…
Forwarded from Molotov Brasil (Dr. Dre Anorexic Rapper λ)
Todos nós sabemos o que está ocorrendo, algo que vou comentar na próxima postagem é a ideia de um "desprendimento" dos softwares gringos, na qual o governo Lula tem um plano para criar um novo "Whatsapp Brasileiro", todos nós sabemos a real intenção por trás desse projeto!
Leiam o conteúdo abaixo, ao final da tarde será postado como realizar a configuração do Orbot para celular.
- Link para o conteúdo!
Leiam o conteúdo abaixo, ao final da tarde será postado como realizar a configuração do Orbot para celular.
- Link para o conteúdo!
Telegraph
Três Macacos Sábios - A censura que fazem não parecer censura.
Segundo a religião budista, os chamados "Três Macacos Sábios", também chamados de "Mizaru", "Kikazaru" e "Iwazara" são a representação de um provérbio japonês que representa "não ver o mal", "não falar o mal" e "não ouvir o mal". Parece bem bonito aos olhos…