1. Please describe the problem:

When I do some action, reproduced by a browser when:
- submitting a form
- uploading file to Google Drive

my system / or sometimes my browser will freeze completely and I'm not able to kill them except force poweroff of the whole machine. When only browser will freeze I'm able to get to journal and I'm able to find a kernel tracebacks there.

```
bře 04 14:18:11 kernel: Call Trace:
bře 04 14:18:11 kernel:  <TASK>
bře 04 14:18:11 kernel:  ? __die_body.cold+0x19/0x27
bře 04 14:18:11 kernel:  ? die+0x2e/0x50
bře 04 14:18:11 kernel:  ? do_trap+0xca/0x110
bře 04 14:18:11 kernel:  ? do_error_trap+0x6a/0x90
bře 04 14:18:11 kernel:  ? __list_add_valid_or_report.cold+0x4b/0x5b
bře 04 14:18:11 kernel:  ? exc_invalid_op+0x50/0x70
bře 04 14:18:11 kernel:  ? __list_add_valid_or_report.cold+0x4b/0x5b
bře 04 14:18:11 kernel:  ? asm_exc_invalid_op+0x1a/0x20
bře 04 14:18:11 kernel:  ? __list_add_valid_or_report.cold+0x4b/0x5b
bře 04 14:18:11 kernel:  free_unref_page_commit+0x94/0x370
bře 04 14:18:11 kernel:  free_unref_folios+0x39b/0x8f0
bře 04 14:18:11 kernel:  folios_put_refs+0x136/0x230
bře 04 14:18:11 kernel:  free_pages_and_swap_cache+0x1d0/0x240
bře 04 14:18:11 kernel:  __tlb_batch_free_encoded_pages+0x45/0xa0
bře 04 14:18:11 kernel:  tlb_finish_mmu+0x79/0x180
bře 04 14:18:11 kernel:  zap_page_range_single+0x13f/0x1d0
bře 04 14:18:11 kernel:  do_madvise+0x153a/0x1810
bře 04 14:18:11 kernel:  ? futex_q_lock+0x2a/0x40
bře 04 14:18:11 kernel:  ? futex_wake+0x8f/0x1b0
bře 04 14:18:11 kernel:  ? __seccomp_filter+0x303/0x520
bře 04 14:18:11 kernel:  ? __x64_sys_madvise+0x2b/0x40
bře 04 14:18:11 kernel:  __x64_sys_madvise+0x2b/0x40
bře 04 14:18:11 kernel:  do_syscall_64+0x82/0x160
bře 04 14:18:11 kernel:  ? futex_wait+0x79/0x120
bře 04 14:18:11 kernel:  ? do_futex+0xcb/0x190
bře 04 14:18:11 kernel:  ? __x64_sys_futex+0x127/0x1e0
bře 04 14:18:11 kernel:  ? syscall_exit_to_user_mode+0x10/0x210
bře 04 14:18:11 kernel:  ? do_syscall_64+0x8e/0x160
bře 04 14:18:11 kernel:  ? do_syscall_64+0x8e/0x160
bře 04 14:18:11 kernel:  ? native_flush_tlb_local+0x30/0x40
bře 04 14:18:11 kernel:  ? flush_tlb_func+0xde/0x290
bře 04 14:18:11 kernel:  ? sched_clock+0x10/0x30
bře 04 14:18:11 kernel:  ? sched_clock_cpu+0xf/0x1f0
bře 04 14:18:11 kernel:  ? irqtime_account_irq+0x3e/0xc0
bře 04 14:18:11 kernel:  ? clear_bhb_loop+0x25/0x80
bře 04 14:18:11 kernel:  ? clear_bhb_loop+0x25/0x80
bře 04 14:18:11 kernel:  ? clear_bhb_loop+0x25/0x80
bře 04 14:18:11 kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
<snip>
bře 04 14:18:11 kernel: list_add corruption. next->prev should be prev (ffff8d08df4beeb0), but was ffffdfe709bd0408. (next=ffffdfe70c31e288).
bře 04 14:18:11 kernel: ------------[ cut here ]------------
bře 04 14:18:11 kernel: kernel BUG at lib/list_debug.c:29!
bře 04 14:18:11 kernel: Oops: invalid opcode: 0000 [#3] PREEMPT SMP NOPTI
bře 04 14:18:11 kernel: CPU: 9 UID: 1000 PID: 5888 Comm: Isolated Web Co Tainted: G      D W          6.13.4-200.fc41.x86_64 #1
bře 04 14:18:11 kernel: Tainted: [D]=DIE, [W]=WARN
bře 04 14:18:11 kernel: Hardware name: LENOVO 20Y4S1QE01/20Y4S1QE01, BIOS N40ET47W (1.29 ) 07/31/2024
```

Complete log will be attached to this bugzilla.

2. What is the Version-Release number of the kernel:
kernel-6.13.4-200.fc41.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

Yes, I'm facing this issue in last few days. However, my rpm-ostree layer from 26.Feb also have this issue.



4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

Mostly, if I open my browser (tested on Brave and Zen) and I try to upload a file to gdrive my system will froze.


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:

To be tested.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.


Reproducible: Always