[BUG] VirtualBox dkms module fails to be installed on 7.2.4-3-cachyos

### Pre-flight checklist

- [x] I have searched existing issues and this is not a duplicate.
- [x] I have read the [Contributing Guidelines](https://github.com/CachyOS/linux-cachyos/blob/master/CONTRIBUTING.md).
- [x] I have verified the issue is reproducible with the latest available CachyOS kernel.
- [x] I have tried to reproduce the issue on Arch Linux's `linux` kernel.

### Upstream / vanilla kernel check

I have not tested with a vanilla/upstream kernel

### Kernel variant

linux-cachyos (EEVDF, Clang)

### System information (cachyos-bugreport.sh)

```text
https://paste.cachyos.org/p/6101058.log
```

### Manual system information (if cachyos-bugreport.sh is unavailable)

```text

```

### Bug description

During system update I got an error while updating a virtualbox dkms module. There was a line to provide this file. After rebooting I cannot start virtual machines.

I'm sorry I'm just a regular user. I'm not even sure I'm using correct words. I don't know how to reproduce the issue on Arch Linux's linux kernel.

[make.log](https://github.com/user-attachments/files/32195178/make.log)

### Steps to reproduce

1. sudo dkms install vboxhost/7.2.16_OSE

### Expected behavior

Command finishes successfully.

### Actual behavior

Sign command: /usr/lib/modules/7.2.4-3-cachyos/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module(s)...(bad exit status: 2)
Failed command:
make -j8 KERNELRELEASE=7.2.4-3-cachyos -C /usr/lib/modules/7.2.4-3-cachyos/build M=/var/lib/dkms/vboxhost/7.2.16_OSE/build LLVM=1

Error! Bad return status for module build on kernel: 7.2.4-3-cachyos (x86_64)
Consult /var/lib/dkms/vboxhost/7.2.16_OSE/build/make.log for more information.

### Logs / stack traces

```text

```

### Additional system information

I don't know if it's relevant but between my previous system update and this system update I was using lavd sched-ext scheduler. However after disabling it I still get this issue.