8000 Fix out of bounds read and write in IO.select by Asmod4n · Pull Request #6711 · mruby/mruby · GitHub
[go: up one dir, main page]

Skip to content

Conversation

@Asmod4n
Copy link
Contributor
@Asmod4n Asmod4n commented Jan 25, 2026

Added error handling for file descriptors larger than FD_SETSIZE in mrb_hal_io_fdset_set and mrb_hal_io_fdset_isset functions, for posix hal.

I actually don't know how to fix this on windows, or if it needs fixing.

Added error handling for file descriptors larger than FD_SETSIZE in mrb_hal_io_fdset_set and mrb_hal_io_fdset_isset functions, for posix hal.

I actually don't know how to fix this on windows, or if it needs fixing.
@Asmod4n Asmod4n requested a review from matz as a code owner January 25, 2026 14:42
@gemini-code-assist
Copy link

Summary of Changes

Hello @Asmod4n, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the robustness of the POSIX HAL's IO.select implementation by introducing critical bounds checking for file descriptors. It addresses a potential vulnerability where file descriptors larger than FD_SETSIZE could lead to out-of-bounds reads or writes, now preventing such issues by raising an argument error.

Highlights

  • File Descriptor Bounds Checking: Implemented checks in mrb_hal_io_fdset_set and mrb_hal_io_fdset_isset to prevent out-of-bounds access when file descriptors exceed FD_SETSIZE.
  • Robust Error Handling: Introduced E_ARGUMENT_ERROR exceptions for cases where a file descriptor is passed that is larger than or equal to FD_SETSIZE, ensuring proper error reporting.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly addresses a critical out-of-bounds read and write vulnerability in IO.select on POSIX systems by adding boundary checks for file descriptors. My review includes suggestions to make these checks more robust by also handling negative file descriptor values, which also lead to undefined behavior. Overall, this is an important security fix.

Copy link
Contributor Author
@Asmod4n Asmod4n left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed both, you know anyone who knows how windows behaves here?

This should fix it for Windows.
@Asmod4n
Copy link
Contributor Author
Asmod4n commented Jan 25, 2026

Found it how it should work on windows and tests still pass :)

@matz matz merged commit d690a49 into mruby:master Jan 27, 2026
18 checks passed
@Asmod4n Asmod4n deleted the patch-4 branch January 27, 2026 10:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0