debug/elf: prevent offset overflow #75522

callthingsoff · 2025-09-18T12:46:20Z

When applying relocations, a malformed ELF file can provide an offset
that, when added to the relocation size, overflows. This wrapped-around
value could then incorrectly pass the bounds check, leading to a panic
when the slice is accessed with the original large offset.

This change eliminates the manual bounds and overflow checks
and writes a relocation to slice by calling putUint.

The putUint helper function centralizes the logic for validating slice
access, correctly handling both out-of-bounds and integer overflow conditions.
This simplifies the relocation code and improves robustness when parsing
malformed ELF files.

Fixes #75516

gopherbot · 2025-09-18T12:51:57Z

This PR (HEAD: c6b2f25) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/705075.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-09-18T13:01:23Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-18T13:10:34Z

Message from Jes Cok:

Patch Set 1: Commit-Queue+1

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-18T13:10:34Z

Message from Go LUCI:

Patch Set 1:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-09-18T12:57:12Z","revision":"7d200899dd12d3e825e9b67bbc3c1ac0597e3dd9"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-18T13:28:41Z

Message from Jes Cok:

Patch Set 1: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-18T13:28:42Z

Message from Go LUCI:

Patch Set 1:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-18T13:28:42Z

Message from Go LUCI:

Patch Set 1: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-18T17:42:54Z

Message from Ian Lance Taylor:

Patch Set 1:

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T10:34:02Z

Message from Jes Cok:

Patch Set 1:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T14:40:15Z

This PR (HEAD: 656e01b) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/705075.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-09-19T14:57:25Z

This PR (HEAD: b7aca22) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/705075.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-09-19T15:24:09Z

This PR (HEAD: 7f9310d) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/705075.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-09-19T16:41:28Z

Message from Jes Cok:

Patch Set 4: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T16:41:29Z

Message from Go LUCI:

Patch Set 4:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-09-19T16:32:17Z","revision":"37119c7b9e761a92178f3f921cdff99ad3b76e20"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T17:06:51Z

Message from Ian Lance Taylor:

Patch Set 4:

(2 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T17:06:51Z

Message from Jes Cok:

Patch Set 4: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T17:06:52Z

Message from Go LUCI:

Patch Set 4:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T17:06:52Z

Message from Go LUCI:

Patch Set 4: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T18:07:45Z

This PR (HEAD: 40ef3a0) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/705075.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-09-19T18:24:38Z

This PR (HEAD: aaa4f90) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/705075.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-09-19T18:32:53Z

Message from Jes Cok:

Patch Set 6: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T18:32:53Z

Message from Go LUCI:

Patch Set 6:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-09-19T18:26:33Z","revision":"7c8e9a7d138d324cce28f80c5d434dc7dc736724"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T18:49:47Z

Message from Jes Cok:

Patch Set 6: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T18:49:48Z

Message from Go LUCI:

Patch Set 6:

This CL has failed the run. Reason:

Tryjob golang/try/gotip-linux-386_debiansid has failed with summary (view all results):

go on master (change 705075)

To reproduce, try gomote repro 8703275823735374721.

Additional links for debugging:

go tool dist test -json output [shard 2]

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-19T18:49:48Z

Message from Go LUCI:

Patch Set 6: LUCI-TryBot-Result-1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-24T06:31:55Z

Message from Go LUCI:

Patch Set 13:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-09-24T06:19:58Z","revision":"8e4cde15f7abb70a8deedef14aab80e3ef101706"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-24T06:32:05Z

This PR (HEAD: 8c9d985) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/705075.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-09-24T06:47:12Z

Message from Go LUCI:

Patch Set 13: LUCI-TryBot-Result-1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-24T06:47:13Z

Message from Jes Cok:

Patch Set 14: Commit-Queue+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-24T06:47:13Z

Message from Go LUCI:

Patch Set 14:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-09-24T06:34:51Z","revision":"02a4b3659079069b97d1a9f1cd1ac6a1e4e0cc32"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-24T06:54:49Z

Message from Jes Cok:

Patch Set 14: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-24T06:54:49Z

Message from Go LUCI:

Patch Set 14:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-24T06:54:50Z

Message from Go LUCI:

Patch Set 14: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-24T19:27:24Z

Message from Ian Lance Taylor:

Patch Set 14:

(3 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

When applying relocations, a malformed ELF file can provide an offset that, when added to the relocation size, overflows. This wrapped-around value could then incorrectly pass the bounds check, leading to a panic when the slice is accessed with the original large offset. This change eliminates the manual bounds and overflow checks and writes a relocation to slice by calling putUint. The putUint helper function centralizes the logic for validating slice access, correctly handling both out-of-bounds and integer overflow conditions. This simplifies the relocation code and improves robustness when parsing malformed ELF files. Fixes golang#75516 Change-Id: I3a1662398a981977d6cbacfa47c40707ddd87b37

gopherbot · 2025-09-25T04:41:18Z

This PR (HEAD: 4914431) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/705075.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2025-09-25T05:08:42Z

Message from Jes Cok:

Patch Set 15: Commit-Queue+1

(3 comments)

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-25T05:16:23Z

Message from Go LUCI:

Patch Set 15:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-09-25T05:02:33Z","revision":"69bb562018057d61455822cc2ea8d0e1c813de96"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-25T05:30:53Z

Message from Jes Cok:

Patch Set 15: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-25T05:30:54Z

Message from Go LUCI:

Patch Set 15:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-25T05:30:54Z

Message from Go LUCI:

Patch Set 15: LUCI-TryBot-Result+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-25T22:40:29Z

Message from Ian Lance Taylor:

Patch Set 15: Code-Review+2 Commit-Queue+1

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-25T22:48:00Z

Message from Go LUCI:

Patch Set 15:

Dry run: CV is trying the patch.

Bot data: {"action":"start","triggered_at":"2025-09-25T22:31:23Z","revision":"69bb562018057d61455822cc2ea8d0e1c813de96"}

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-25T23:03:11Z

Message from Ian Lance Taylor:

Patch Set 15: -Commit-Queue

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-25T23:03:12Z

Message from Go LUCI:

Patch Set 15:

This CL has passed the run

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-26T06:59:56Z

Message from Florian Lehner:

Patch Set 15: Code-Review+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-26T17:18:55Z

Message from Junyang Shao:

Patch Set 15: Code-Review+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-26T17:36:33Z

Message from Michael Knyszek:

Patch Set 15: Code-Review+1

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-27T01:25:24Z

Message from Jes Cok:

Patch Set 15:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

When applying relocations, a malformed ELF file can provide an offset that, when added to the relocation size, overflows. This wrapped-around value could then incorrectly pass the bounds check, leading to a panic when the slice is accessed with the original large offset. This change eliminates the manual bounds and overflow checks and writes a relocation to slice by calling putUint. The putUint helper function centralizes the logic for validating slice access, correctly handling both out-of-bounds and integer overflow conditions. This simplifies the relocation code and improves robustness when parsing malformed ELF files. Fixes #75516 Change-Id: I00d806bf5501a9bf70200585ba4fd0475d7b2ddc GitHub-Last-Rev: 4914431 GitHub-Pull-Request: #75522 Reviewed-on: https://go-review.googlesource.com/c/go/+/705075 Reviewed-by: Florian Lehner <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Junyang Shao <[email protected]> Auto-Submit: Ian Lance Taylor <[email protected]> Reviewed-by: Michael Knyszek <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Commit-Queue: Ian Lance Taylor <[email protected]>

gopherbot · 2025-09-29T04:40:16Z

Message from Jes Cok:

Patch Set 15:

(1 comment)

Please don’t reply on this GitHub thread. Visit golang.org/cl/705075.
After addressing review feedback, remember to publish your drafts!

gopherbot · 2025-09-29T04:48:02Z

This PR is being closed because golang.org/cl/705075 has been merged.

austinderek mentioned this pull request Sep 18, 2025

debug/elf: prevent out-of-bounds access in applyRelocations PullRequestInc/go#80

Closed

callthingsoff force-pushed the elf_range_check branch from c6b2f25 to 656e01b Compare September 19, 2025 14:39

callthingsoff changed the title ~~debug/elf: prevent out-of-bounds access in applyRelocations~~ debug/elf: use saferio.InBounds to prevent offset overflow Sep 19, 2025

callthingsoff force-pushed the elf_range_check branch from 656e01b to b3c1976 Compare September 19, 2025 14:43

callthingsoff force-pushed the elf_range_check branch from 7f9310d to 40ef3a0 Compare September 19, 2025 18:04

callthingsoff force-pushed the elf_range_check branch from 8c9d985 to 4914431 Compare September 25, 2025 04:40

gopherbot closed this Sep 29, 2025

callthingsoff deleted the elf_range_check branch September 29, 2025 04:49

debug/elf: prevent offset overflow #75522

debug/elf: prevent offset overflow #75522

Conversation

callthingsoff commented Sep 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 18, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 19, 2025

Uh oh!

gopherbot commented Sep 24, 2025

Uh oh!

gopherbot commented Sep 24, 2025

Uh oh!

gopherbot commented Sep 24, 2025

Uh oh!

gopherbot commented Sep 24, 2025

Uh oh!

gopherbot commented Sep 24, 2025

Uh oh!

gopherbot commented Sep 24, 2025

Uh oh!

gopherbot commented Sep 24, 2025

Uh oh!

gopherbot commented Sep 24, 2025

Uh oh!

gopherbot commented Sep 24, 2025

Uh oh!

gopherbot commented Sep 25, 2025

Uh oh!

gopherbot commented Sep 25, 2025

Uh oh!

gopherbot commented Sep 25, 2025

Uh oh!

callthingsoff commented Sep 18, 2025 •

edited

Loading