Although you implied you might be looking for a book to read, I would suggest reviewing the notes you already have, even if it requires skimming past excess details here and there, could be a much more useful first step.
I'm sure you've covered quite a number of topics, not all of which will be equally useful to you in the future. In practical terms, quite a lot of what you have studied won't be applicable to the particular job you end up doing, let alone interviewing for that posision. Your degree hopefully gives you quite a bit of breadth which will afford you a variety of directions being open to you in the future, however to get hired for a job, you usually need to demonstrate depth of knowledge in specific areas rather than focusing on the breadth. Everything else, you will have the luxury of time (often on the clock even) to go back and review when you actually figure out why its useful to review.
I don't think I've ever had a technical interview that hasn't had questions on data structures and algorithms, for example, but for the types of positions I've applied for I've never been asked about specifics from operating systems, analog systems, etc. Know your data structures solidly, know their big-o time costs for insert, delete, find, and which ones are useful for solving which kinds of problems. Review key topics about the programming language you are applying for jobs in (eg: for java I might review things like inheritance, interfaces, and threading)
If you didn't make study-guides for individual courses when you were studying for your final exams, now would be a great time to go back and skim through the course notes and pick out the "important stuff" and make a to the point "cheat-sheet" you can study and review before interviews.
For data structures, for example, you could make a big chart comparing time costs for certain key operations, make another list that summarizes the pros and cons of each individual data structure. Maybe a brief summary of how that data structure works if you are likely to forget that. Actually taking the time to write (or type) that out (not copy and paste) will help it to sink into your long term memory.
Go through all the notes and materials you have, skimming or skipping over superflouous topics, marking up with notes in the margins about where in the notes important topics are, and decide which materials are even worth saving in the first place. The others either make it hard to find the important stuff, or just become heavy clutter you end up lugging around the next seven times you move, until you toss them.
Think about reviewing from the perspective you would have had studying for final exams, what material out of everything covered was actually important? How could I gather together the most important parts so I don't forget them? For some people, that might mean taking a highligher and pile of post-its to the lecture slides and marking where to start reading about key topics to brush up. For others that might mean writing out in your own words a summary of the key points. Ideally, I would have suggested having already made study guides for yourself in preparing for individual final exams, so that at this point you would only be filtering through your final exam review notes to pick topics to retain.
Periodic review over time is one of the best ways to secure things into long term memory, so creating materials now to facilitate periodic review will help you not lose the recall of important information you've studied. But not everything is important, many things can just be looked up or reviewed if and when they come up in the real world.
Also, I would focus on things you already know, but that aren't so obvious you know them point blank. If there's stuff you "should have covered" but genuinely just don't know, unless its highly relevant to interviews, I would make it a low priority. Not everyone has the same background, or the same knowledge, so the key to interviewing is to convince the interviewer that what you DO know, you know well, and so you can interview confidently. You're never going to know everything, so focus on presenting a solid knowledge of the things you do know.