vboxdrv kernel error msgs (Fedora 38 kernel 6.6.4 + VB 7.0.12)

[spamrefuse]

When running a Windows 10 guest, I get kernel messages in the journal, like below.
The host is on an up-to-date Fedora 38 OS with kernel 6.6.4. VB is version 7.0.12.
Is this a bug in VB and/or in the vboxdrv module?

== START =====================================
Dec 09 20:16:46 kernel: warning: `nspr-2' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211
Dec 09 20:16:54 kernel: SUPR0GipMap: fGetGipCpu=0x1b
Dec 09 20:16:55 kernel: ------------[ cut here ]------------
Dec 09 20:16:55 kernel: WARNING: CPU: 1 PID: 3470 at /tmp/vbox.0/r0drv/linux/memobj-r0drv-linux.c:564 rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv]
Dec 09 20:16:55 kernel: Modules linked in: snd_seq_dummy snd_hrtimer tun tls vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) it87 hwmon_vid rtl8xxxu rtl8192cu rtl_usb rtl8192c_common rtlwifi mac80211 snd_hda_codec_realte
k snd_hda_codec_generic ledtrig_audio snd_hda_intel libarc4 snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec cfg80211 snd_hda_core snd_hwdep vfat fat snd_seq snd_seq_device snd_pcm snd_timer rfkill snd intel_rapl_msr intel_rapl_commo
n x86_pkg_temp_thermal soundcore intel_powerclamp coretemp kvm_intel kvm iTCO_wdt irqbypass rapl intel_cstate intel_pmc_bxt intel_uncore mei_pxp mei_wdt iTCO_vendor_support mei_hdcp at24 mei_me i2c_i801 mei lpc_ich pcspkr i2c_smbus lo
op fuse i915 crct10dif_pclmul crc32_pclmul crc32c_intel polyval_clmulni polyval_generic ghash_clmulni_intel i2c_algo_bit sha512_ssse3 drm_buddy ttm sha256_ssse3 drm_display_helper sha1_ssse3 atl1c cec video wmi serio_raw
Dec 09 20:16:55 kernel: CPU: 1 PID: 3470 Comm: EMT-0 Tainted: G OE 6.6.4-100.fc38.x86_64 #1
Dec 09 20:16:55 kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./B75-D3V, BIOS F9 10/23/2013
Dec 09 20:16:55 kernel: RIP: 0010:rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv]
Dec 09 20:16:55 kernel: Code: 83 ff 40 74 25 48 89 c7 48 21 f7 48 85 d2 75 1c 48 89 f8 0f 1f 00 48 89 c6 48 89 cf e8 2e 5a 0c c5 90 31 c0 5d c3 cc cc cc cc <0f> 0b f6 c2 01 75 15 48 f7 d0 48 89 c7 48 21 f7 48 81 e7
00 f0 ff
Dec 09 20:16:55 kernel: RSP: 0018:ffffc90001b5fd20 EFLAGS: 00010246
Dec 09 20:16:55 kernel: RAX: 0000000167956000 RBX: ffff88814d9d8858 RCX: ffff88814d9d8850
Dec 09 20:16:55 kernel: RDX: 0000000000000061 RSI: 000fffffffffffff RDI: 0000000000000040
Dec 09 20:16:55 kernel: RBP: ffffc90001b5fd20 R08: ffffc90002ac2000 R09: ffff8881449f8c90
Dec 09 20:16:55 kernel: R10: ffffc90002ac2000 R11: 00000001003e0003 R12: 0000000000000001
Dec 09 20:16:55 kernel: R13: ffffffffc0fcb6b0 R14: ffffc9000290a000 R15: ffffc90001b5fde8
Dec 09 20:16:55 kernel: FS: 00007fddfb9806c0(0000) GS:ffff88840e480000(0000) knlGS:0000000000000000
Dec 09 20:16:55 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 09 20:16:55 kernel: CR2: 00007fdde4ff9000 CR3: 00000001449f8003 CR4: 00000000001706e0
Dec 09 20:16:55 kernel: Call Trace:
Dec 09 20:16:55 kernel: <TASK>
Dec 09 20:16:55 kernel: ? rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv]
Dec 09 20:16:55 kernel: ? __warn+0x81/0x130
Dec 09 20:16:55 kernel: ? rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv]
Dec 09 20:16:55 kernel: ? report_bug+0x171/0x1a0
Dec 09 20:16:55 kernel: ? handle_bug+0x3c/0x80
Dec 09 20:16:55 kernel: ? exc_invalid_op+0x17/0x70
Dec 09 20:16:55 kernel: ? asm_exc_invalid_op+0x1a/0x20
Dec 09 20:16:55 kernel: ? __pfx_rtR0MemObjLinuxApplyPageRange+0x10/0x10 [vboxdrv]
Dec 09 20:16:55 kernel: ? rtR0MemObjLinuxApplyPageRange+0x6b/0xa0 [vboxdrv]
Dec 09 20:16:55 kernel: __apply_to_page_range+0x3d2/0x900
Dec 09 20:16:55 kernel: rtR0MemObjNativeProtect+0x80/0xc0 [vboxdrv]
Dec 09 20:16:55 kernel: VBoxHost_RTR0MemObjProtect+0x8b/0xc0 [vboxdrv]
Dec 09 20:16:55 kernel: supdrvIOCtl+0x2cad/0x31b0 [vboxdrv]
Dec 09 20:16:55 kernel: VBoxDrvLinuxIOCtl_7_0_12+0x169/0x260 [vboxdrv]
Dec 09 20:16:55 kernel: __x64_sys_ioctl+0x97/0xd0
Dec 09 20:16:55 kernel: do_syscall_64+0x60/0x90
Dec 09 20:16:55 kernel: entry_SYSCALL_64_after_hwframe+0x6e/0xd8
Dec 09 20:16:55 kernel: RIP: 0033:0x7fde31a1fecd
Dec 09 20:16:55 kernel: Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00
Dec 09 20:16:55 kernel: RSP: 002b:00007fddfb97ed20 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Dec 09 20:16:55 kernel: RAX: ffffffffffffffda RBX: 00007fdde4d37010 RCX: 00007fde31a1fecd
Dec 09 20:16:55 kernel: RDX: 00007fdde4d37010 RSI: 0000000000005684 RDI: 0000000000000007
Dec 09 20:16:55 kernel: RBP: 00007fddfb97ed70 R08: 0000000000000000 R09: 00007fddfb97ec00
Dec 09 20:16:55 kernel: R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fddfbecc968
Dec 09 20:16:55 kernel: R13: 0000000000000000 R14: 00007fddc0000b70 R15: 00007fde316c5370
Dec 09 20:16:55 kernel: </TASK>
Dec 09 20:16:55 kernel: ---[ end trace 0000000000000000 ]---
Dec 09 20:16:55 kernel: vboxdrv: 0000000055f0ad77 VMMR0.r0
Dec 09 20:16:56 kernel: vboxdrv: 00000000607ca656 VBoxDDR0.r0
== END =====================================

-Stub

[scottgus1]

If the Linux kernel version came out after the Virtualbox version, then you'll need to wait for a new Virtualbox version, or try the test builds and development snapshots.

[WFV]

@ spamrefuse.
Seeing essentially same error in Arch host, with Ubuntu, Fedora, Arch, WinXP and Win7 guests. Started after a kernel update (as scottgus1 mentions). I've run memtest86 at host boot up and find no memory errors. Doesn't seem to cause any noticeable issues beyond the error message in either host nor guests. Linux guest journals report same error.

UPDATE: problem persists in 7.0.14

[birdie]

You'd think Oracle might have fixed it in 7.0.14 but no:

https://www.virtualbox.org/ticket/21964

and also here:

https://www.virtualbox.org/ticket/21952

Is this a bug in VB and/or in the vboxdrv module?

That's a bug in the vboxdrv module.