Comment 5 for bug 2058480

This may have already been fixed upstream in December 2023: this commit to xen-project/xen looks extremely relevant, because it purports to fix an UBSAN issue with the exact same error text as this issue ("UBSAN: index 1 is out of range for type 'xen_netif_rx_sring_entry [1]'"):

https://github.com/xen-project/xen/commit/93d913c6e66e01597681d0a456c1523279218524

I am way out of my depth here, but as I understand it, these xen files get vendored into the Linux codebase:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=125c0a646a257fd58de223f2c3e1fe8a99085644

...and from there, they get copied into the git repos for both Ubuntu's `linux` and `linux-aws` packages. Here's one of the affected files in the Jammy LTS repos, and it definitely hasn't been patched because it was last updated in 2021:

- linux: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/log/include/xen/interface/io/ring.h
- linux-aws: https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-aws/+git/jammy/log/include/xen/interface/io/ring.h

That bugfix is also missing from the Mantic repos -- though I haven't personally verified that it's causing issues for Mantic as well.